This repository has been archived by the owner on Oct 4, 2023. It is now read-only.
Pass retry through for client handle validation #2192
Merged
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.
Description
Iteration on #2183
Because
404
response codes trigger a discovery node reelection, the check for user not existing will trigger this logic and results in longer method response times.This change is to pass along a flag for
retry
so that checking for an existing handle will not trigger reslection and be instant!Not sure if there's a mobile component to this that I'm missing @sliptype
Fixes PLAT-432
Dragons
Is there anything the reviewer should be on the lookout for? Are there any dangerous changes?
How Has This Been Tested?
Ran locally against stage and validated that no re-selection were happening for non-existent handles.
How will this change be monitored?
For features that are critical or could fail silently please describe the monitoring/alerting being added.
Feature Flags
Are all new features properly feature flagged? Describe added feature flags.