cassandra/docker-compose: go back to using the latest cassandra version

In January the tests started failing on Cassandra `4.1`, so we pinned the cassandra version to `4.0.7`, which didn't have these problems. `4.0.7` is the version that we've been using in the CI since then. In the meantime there were new releases of `Cassandra`, at the moment the latest is `4.1.3`. Let's try to go back to the latest version, maybe the problems fixed themselves during the last nine months. Refs: #620 Refs: #629 Fixes: #633 Signed-off-by: Jan Ciolek <[email protected]>
scylladb · Oct 19, 2023 · 9fbb37e · 9fbb37e
1 parent 2641d1b
commit 9fbb37e
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/test/cluster/cassandra/docker-compose.yml b/test/cluster/cassandra/docker-compose.yml
@@ -10,7 +10,7 @@ networks:
         - subnet: 172.42.0.0/16
 services:
   cassandra1:
-    image: cassandra:4.0.7
+    image: cassandra
     healthcheck:
         test: ["CMD", "cqlsh", "-e", "describe keyspaces" ]
         interval: 5s
@@ -24,7 +24,7 @@ services:
       - HEAP_NEWSIZE=512M
       - MAX_HEAP_SIZE=2048M
   cassandra2:
-    image: cassandra:4.0.7
+    image: cassandra
     healthcheck:
         test: ["CMD", "cqlsh", "-e", "describe keyspaces" ]
         interval: 5s
@@ -42,7 +42,7 @@ services:
       cassandra1:
         condition: service_healthy
   cassandra3:
-    image: cassandra:4.0.7
+    image: cassandra
     healthcheck:
         test: ["CMD", "cqlsh", "-e", "describe keyspaces" ]
         interval: 5s