Restore retries for stores to remote REAPI byte stores (Cherry-pick of #19737) #19798
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 #19732 by restoring the retries when storing hits retryable server failures from the REAPI remote cache server, which were lost in the #19050 refactoring.
This also explicitly tests for retries, refactoring
StubCAS
to generaliseread_request_count
to expose the counts of more requests than just reads, and also consistently return aStatus::internal(...)
for the simulated errors.I think #19050 fortunately landed just after 2.17 was cut, so this regression only affects the 2.18 pre-releases.