The (eventual) upgrade to Cassandra 4.x may block upgrading nodes to Bullseye (see: T310980: Allow Cassandra to be deployed on Bullseye nodes), and would create the opportunity to stop issuing instance-specific IP addresses (see: T269328: Cassandra instance DNS records - are they needed?). We should begin investigating what an upgrade/migration will entail.
Customize query in gerrit
|Resolved||Eevans||T313814 Upgrade to Cassandra 4.x|
|Resolved||Eevans||T337344 Upgrade cassandra-dev cluster to Cassandra 4.1.1|
|Resolved||Eevans||T337426 Upgrade sessionstore cluster to Cassandra 4.1.1|
|Open||None||T337901 Upgrades to Cassandra 4.1.1 fail with NullPointerException|
|Resolved||Eevans||T338639 Move check_ssl port to 7000 for Cassandra >= 4.1.1|
|Resolved||Eevans||T339298 Upgrade restbase cluster to Cassandra 4.1.1|
|Resolved||Eevans||T344210 restbase1030: Cassandra crashing (signal 11)|
|Resolved||Eevans||T339299 Upgrade aqs cluster to Cassandra 4.1.1|
|Resolved||Eevans||T339300 Upgrade ml-cache cluster to Cassandra 4.1.1|
- Mentioned In
- rLPRIa1724136e7d5: cassandra: add dummy secrets for services-dev (test env)
T331714: Migrate sessionstore servers to Bullseye
T331713: Migrate restbase servers to Bullseye
T331712: Migrate ml-cache to Bullseye
T331711: Migrate cassandra-dev to Bullseye
- Mentioned Here
- T269328: Cassandra instance DNS records - are they needed?
T310980: Allow Cassandra to be deployed on Bullseye nodes
Apologies; This is a priority (there is even an associated KR for this quarter), we just haven't got there yet. :(
That's great! We also have the cassandra-dev cluster now to work with.