Aerospike Version, any other major upgrades before 3.13.x necessary? - aerospike

Our Enterprise AS cluster is on v 3.7.3, do we need to upgrade to any of the versions before 3.13.x or can we directly upgrade to the major 3.13.x version?

Nope, shouldn't be a problem to upgrade from 3.7 to 3.13.
Note: As an Enterprise user you have access to our 24 hr support team at support.aerospike.com.

Related

Can we install OpenJDK-11 in Redhat Enterprise Linux-7.x O/S version

I am currently running my Java based applications with OpenJDK1.8 and RHEL [Redhat Enterprise Linux] - 7.9. I am planning to upgrade few of the Java native libraries into higher versions whereas I need to upgrade my Java version to OpenJDK11 in that case.
Can anyone suggest whether OpenJDK11 compatible with RHEL-7.9 ? I don't have a plan to upgrade my RHEL version into RHEL-8.x.

ScyllaDB: Can I have multi DC cluster with different Scylla versions?

Currently I have a single DC cluster with 3 nodes running 4.1.7 version of Scylla. This setup has been running for a long time and I don't want to make changes to this DC, if possible. Now I have a requirement to add another DC cluster with 3 nodes. Can I set up this new DC with the latest stable version of Scylla? Will the two DCs be able to communicate with each other without any issues? Or am I forced to upgrade the existing DC to the latest version?
Scylla supports rolling upgrades, which means you can indeed upgrade just some of the nodes in the cluster while the rest are still running the older version. The cluster should be able to fully work in this state - including the communication between old and new nodes. Not all upgrade paths are equally supported or have been equally tested, obviously, but most "interesting" upgrade paths (a newer release in the same major version, the next major version) are indeed supported.
That being said, while staying at a half-upgraded state for a long time is possible, it is not recommended. It also means that whatever new features or improved algorithms were introduced in the new version, the new nodes will need to avoid them until the full cluster is upgraded.
OSS 4.1.7 is a pretty old OSS release from Oct 2020. The assumption that you can add another DC running OSS 5.0 (latest OSS release from 10 days ago) to the existing cluster, is a bit of a risky one.
The supported upgrade path (QA tested) is from OSS 4.6 to 5.0. You can read more about the upgrade path here: https://docs.scylladb.com/upgrade/upgrade-opensource/
The tested upgrade route is via minor versions 4.1 --> 4.2 --> 4.3 --> 4.4 --> 4.5 --> 4.6 --> 5.0, jumping multiple minor version should work, but we can't say that it was tested.

What are the currently supported redis versions? (latest stable 6.0.6)

Redis release cycle page states
Support
Older versions are not supported as we try very hard to make the Redis API mostly backward compatible. Upgrading to newer versions is usually trivial.
For example, if the current stable release is 2.6.x, we accept bug reports and provide support >for the previous stable release (2.4.x), but not for older ones such as 2.2.x.
When 2.8 becomes the current stable release, the 2.6.x will be the oldest supported release.
Does this mean that currently supported versions are 6.0 (latest stable version 6.0.6) and 5.0 (previous stable version 5.0.9), and older versions such as (4.0.x, 3.2.x, 2.8.x) are not supported?
Thanks in advance.

Bigcommerce | Stencil - Why is the recommended node version for windows so old?

The Stencil pre-requisites page recommends only installing LTS versions of node, and the specifically recommends Node 4.4.0 for the Mac and 4.1.2 for Linux.
However for Windows the recommended version is 0.12.7 even though the current LTS is 4.4.5. Is there a particular issue on Windows with newer versions or is the documentation just outdated?
Those are the latest BigCommerce-tested versions on each operating system. You can try the current LTS, but issues may arise.

Does the new Nexus 3.0 OSS release support rpm repo?

I am looking at Nexus 3.00 OSS Edition.
The recent release of Nexus 3.0 (OSS Edition) seems to have dropped support for rpms.
I don't see any specific note declaring that they are going to be dropping some features from 2.x.
So i am not sure whether the rpm/ yum repositry support is actually removed Or is it being supported differently with the new Nexus 3.0 or this feature has been made exclusive for the Paid version.
Not yet. The progress of this can be tracked in http://issues.sonatype.org/browse/NEXUS-10191. Feel free to watch for release details.