CXXCBC-482: Range scan orchestrator should use best effort retry strategy by default #542
Conversation
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
avsej
approved these changes
Mar 11, 2024
Member
looks like mozilla just updated certificate bundles, and we were unlucky to pickup some stale caches. I believe it should be fixed when restarted |
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.
The retry strategy is unset instead of being set to best-effort by default.
This has been found via the custom transcoder FIT tests which create a collection and immediately perform a range scan on them, where the SDK fast-fails instead of retrying the get_collection_id operation (which uses the retry strategy specified in the orchestrator).