-
Notifications
You must be signed in to change notification settings - Fork 801
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade cassandra image to 4.1.3 in docker compose files #5461
Upgrade cassandra image to 4.1.3 in docker compose files #5461
Conversation
d874c8e
to
ae3a3df
Compare
- "7943:7933" | ||
- "7944:7934" | ||
- "7945:7935" | ||
- "7949:7939" | ||
- "7843:7833" | ||
environment: | ||
- "CASSANDRA_SEEDS=cassandra" | ||
- "PROMETHEUS_ENDPOINT_0=0.0.0.0:9000" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
avoiding usage of port 9000 because it's a popular port and high chance of conflict. (I encountered this issue)
ae3a3df
to
a517566
Compare
This is causing versioning issues when using docker-compose.yml to spin up the container -
|
You might have a previous sha of
|
What changed?
Docker compose files were referring to an older version (3.11) of Cassandra. Updated them with current GA version 4.1.3.
ubercadence/server:master-auto-setup container's initialization script waits on Cassandra to be up and corresponding wait command is updated to use
--cqlversion=3.4.6
(previously 3.4.4).Misc change: I was also interested in to see Cassandra's full query logs. Added
docs/howtos/cassandra-fql.md
to explain the steps on how to check FQL.Why?
To keep things up to date. Assuming Cassandra 4+ is more widely used.
How did you test it?
make test
and bench testsPotential risks
Users who depends on
ubercadence/server:master-auto-setup
should pull new image before running docker-compose. Hopefully this is only used for development/discovery use cases. Left a note in changelog for this.