Possible fix for Cassandra / Kairos problems on staging? #283
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ing over on staging
Closed
timcowlishaw
force-pushed
the
chore/docker-compose-upgrade
branch
from
c4881d9 to
6f461ca
Compare
|
Testing in staging. The outcome is that kairos waits for cassandra-1 to be healthy and then starts. So far so good!
|
timcowlishaw
force-pushed
the
chore/docker-compose-upgrade
branch
from
6f461ca to
196ba48
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Not for merging because untested (and based off the new compose file branch which isn't yet merged), but this might be a simple solution to #268 - give cassandra a healthcheck in the docker compose file which would allow it to reboot if it becomes unresponsive, and specify that kairos depends on it being healthy, so it cleanly starts and restarts in response.