Skip to content
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

Unify cassandra setup in docker-compose #5482

Merged
merged 1 commit into from
Dec 18, 2023

Conversation

3vilhamster
Copy link
Member

What changed?
I've set limits for java heap size to shrink cassandra memmory allocation.
Also, unified all cassandra images in docker-compose files with the same values for heap, healthchecks and depends_on

Why?
To have a sane and unified way to run minimal local/ci cassandra setup.

How did you test it?
Local docker-compose up and local docker/buildkite run

Potential risks

Release notes

Documentation Changes

Copy link
Member

@Groxx Groxx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

C* running memory drops from 2GB+ to ~1GB, so I'm kinda curious why it's so much higher than the listed values... but yeah! Seems to work great, and I can even launch docker-compose.yml with only 2GB allocated to Docker. Big improvement.

@@ -3,10 +3,18 @@ version: "3.5"
services:
cassandra:
image: cassandra:4.1.3
environment:
- "MAX_HEAP_SIZE=256M"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks!

@3vilhamster 3vilhamster merged commit 07018fe into cadence-workflow:master Dec 18, 2023
16 checks passed
@3vilhamster 3vilhamster deleted the shring-cassandra branch December 18, 2023 09:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants