we have a cassandra node with 3.9 version.
Is it possible to migrate to last stable version (3.0.11)?
(we dont use any special feature of 3.9.)
Please read downgrade session of this guide:
https://wiki.apache.org/cassandra/CompatibilityGuarantees
The main part:
Downgrading is only guaranteed within minor releases and only to the previous bug-fix release
Theoretically you can try downgrading 3.9 -> 3.7 -> 3.5... etc, but there is no grantees that this will work and will not do problems in the future. Test in some dev environment if you have to do it, or stay with 3.9...
Related
The IntelliJ IDEA told me that the current version we chose 4.0.1 has security vulnerability, and it recommends developer to upgrade org.glassfish to newer version.
Could we do that? I tested version 4.0.2, it works. But, would it still work for further lab/assignment?
Thanks.
We are trying to upgrade Rundeck version from 3.0.27 to the latest version (3.4.7)
We got below questions,
What is the approach to upgrade from 3.0.xxxx to 3.4.7? Could we do a direct upgrade or otherwise, if we have to run through multiple intermediary versions, what are those?
Does upgrading from 3.0.xxx to 3.4.7 fix the log4j vulnerability?
Please help to clarify above.
Thanks
Due to the big gap between 3.0.X and 3.4.X (and the upcoming 4.0.X) the best way to upgrade your instance is to create a fresh 3.4/4.0 instance and then import your projects and keys (exported previously), as a tip, try this on a non-prod environment first.
Rundeck 3.0.x uses log4j 1, so, even if the vulnerability doesn't affect explicitly the log4j 1.x EOL was in 2015 and isn't supported anymore, so, it's important to move to the latest version (Rundeck 3.4.10 at this moment).
I have Critical Updates available on my DNN v06.01.03(108).
AS per Security Center I should get upgraded to 7.4.1.
My Question is - do I need to do upgrade directly to 7.4.1 or in steps?
For e.g. 6.1.3 -> 6.2.9 -> 7.4.1
I would upgrade directly from 6.1.3 to 7.3.4.
Always back up your database and the file system before an upgrade, it is recommended that you do the upgrade in a test environment first, but if you don't have access to a test environment you can always restore to 6.1.3 from your backups if necessary.
Chris
I'm trying to understand restrictions of upgrade from/to different versions of cassandra.
On the one hand, Cassandra docs
http://docs.datastax.com/en/upgrade/doc/upgrade/cassandra/upgradeC_c.html
are saying "Cassandra 3.0.x restrictions: Upgrade from Cassandra 2.1 versions greater or equal to 2.1.9...", and I understand that as 'you couldn't upgrade to 3.0 from 2.1.8 and prior 2.1.* versions'.
On the other hand, there are no any restrictions on upgrading from, say, 2.1.8 (version prior to 2.1.9) to 2.1.11 (version grater then 2.1.9), in particular, 2.1.8->2.1.11 upgrade don't require upgrade of sstables.
So, could someone explain, why it's possible to upgrade from 2.1.9 to 3.0 but not from 2.1.8 to 3.0?
The docs restrict you from upgrading from early 2.1 versions to 3.0 because there are bug fixes and stability improvements in the later 2.1 releases that affect upgrades.
The best practice is to go to the latest patch on your branch before upgrading a major release. I.E. go to the latest 2.1.x and then go to 3.0.
Note: 3.0.0 dropped last night and it is very early in its release cycle. Make sure you test thoroughly in a qa environment before upgrading your production instance and follow the upgrade docs carefully.
when I run
node -v
I got 4.2.1 which is very strange since I remember I worked with 0.10 versions: I am totally lost with nodejs versions
reading the pm2 doc
Warning: If you want to use the embedded load balancer (cluster mode),
we recommend the use of node#0.12.0+ or node#0.11.16+. We do not
support node#0.10.*'s cluster module anymore.
I don't understand how node.js versions works: looks like we jumped form 0.10
to 4.2
Does pm2 works with latest version of node.js ?
regards
don't understand how node.js versions works: looks like we jumped form 0.10 to 4.2
When io.js and node.js merged, then node.js jump directly to 4.x series. This happened due to difference in versions of io.js (3.x series) and node.js (0.x series). So next common version was named 4.x series and this lead to some confusion. See this announcement.
Does pm2 works with latest version of node.js ?
You can give it a try yourself, but IMO it should work well.
At the end of 2014, node was forked into io.js for reasons I won't cover here.
The io.js project adopted the semver notation and, as the pace of changes was very fast (we got all the recent advances of ES6 that were already available in V8), came to version 3.
In september 2015, io.js was merged back into node, and it was decided to keep the semver versionning, and to go to version 4. More details here, including the LTS.
This makes it possible to deal with a monotonous version order, thus a 4.0 version of node is greater than a 0.11 version. But be wary, many changes were introduced and the ecosystem is big. You'll probably have changes to do when going from 0.x to a new version, especially if you use many modules.