fix(bigtable): retries for CheckConsistency
/ AsyncWaitForConsistency
#10955
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.
Part of the work for #10413
Default
BigtableTableAdmin::(Async)CheckConsistency
to be idempotent. This will improve the success rate for thebigtable_admin::AsyncWaitForConsistency(...)
helper.This probably "fixes" #9870. Getting
UNAVAILABLE
is a fairly common flake when run against production in our CI.This change is