Harden three_logserver_seal_empty by retrying on retryable seal error#2873
Merged
tillrohrmann merged 2 commits intorestatedev:mainfrom Mar 10, 2025
Merged
Harden three_logserver_seal_empty by retrying on retryable seal error#2873tillrohrmann merged 2 commits intorestatedev:mainfrom
tillrohrmann merged 2 commits intorestatedev:mainfrom
Conversation
tillrohrmann
force-pushed
the
issues/2871
branch
4 times, most recently
from
e10aab2 to
607e834
Compare
Instead of checking that the StorageState is not empty (meaning not being in storage state disabled), we are checking that we are not provisioning. This ensures that the log servers are provisioned once the cluster health checks pass.
tillrohrmann
force-pushed
the
issues/2871
branch
from
607e834 to
91f3839
Compare
jackkleeman
approved these changes
Mar 10, 2025
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This fixes #2871.