This repository has been archived by the owner on Aug 23, 2023. It is now read-only.
Harden index load against failures on startup #2038
Merged
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
|
Note: we've been running this in prod for a long time now and have seen a large reduction in startup failures. |
robert-milan
approved these changes
Aug 11, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
After a cassandra crash, invalid index entries caused MT to crash repeatedly. Additionally, there were spurious timeouts and metrictank cannot start if any partition failed to load. With even a low chance of partition failure (e.g. 10%) and 16 partitions to load, it's likely Metrictank will fail to start several times. Add some retries so that it's much more likely all partitions succeed.