Closed czchen closed 8 years ago
The core team has no plans to change this behavior for 2 reasons. 1) ComboAMI is intended to make building short-lived test-clusters easy. There are lots of complex maintenance tasks related running a Cassandra cluster that it doesn't help with, and for long-lived clusters you're better of simply installing packages or using the standalone installer yourself. 2) With Cassandra 3.0, the tick/tock rapid release cycle means the end of long-lived bugfix branches. Every other release will bring new features and some upgrade risk, it's best to simply control when/how upgrades happen.
The suggested workaround is to put a "hold" on the affected packages as described in https://help.ubuntu.com/community/PinningHowto This will prevent all automatic upgrades and enable you to control exactly when upgrades happen, and the starting/ending versions.
The current
/etc/apt/sources.list.d/datastax.sources.list
uses the following configuration:It is very dangerous since
apt full-upgrade
will upgrade from2.2
to3.0
without user notices it. It shall uses the suite like2.2
,3.0
to fix the Cassandra version so thatapt full-upgrade
will only upgrade for bug fix, but not new stable release.