Officially, Cassandra supports running with Java 11 (https://cassandra.apache.org/doc/4.1/cassandra/getting_started/java11.html), which doesn't ship in Bookworm. I reckon that Java 17 ought to work —we could test it and see how things go— but if we're the only ones then there will always be risk. @MoritzMuehlenhoff, what are our options for Java 11? Would we be able to import it from unstable? What would security support mean?

In T357791#9551331, @Eevans wrote:

Officially, Cassandra supports running with Java 11 (https://cassandra.apache.org/doc/4.1/cassandra/getting_started/java11.html), which doesn't ship in Bookworm. I reckon that Java 17 ought to work —we could test it and see how things go— but if we're the only ones then there will always be risk. @MoritzMuehlenhoff, what are our options for Java 11? Would we be able to import it from unstable? What would security support mean?

We can't just import from unstable, it would need to be rebuilt (and that would need to happen for every security update as well), so that's a large chunk of work to commit to. We can however simply give things a try on bullseye before the update: Bullseye ships Java 11 and 17 and cassandra uses the Java profile, so we can switch single nodes of the existing Cassandra clusters to Java 17 on Bullseye to test this.

Change #1325922 had a related patch set uploaded (by Eevans; author: Eevans):

[operations/puppet@production] aptrepo: Create cassandra50 bookworm component

https://gerrit.wikimedia.org/r/1325922

Change #1325922 merged by Eevans:

[operations/puppet@production] aptrepo: Create cassandra50 bookworm component

https://gerrit.wikimedia.org/r/1325922