HDDS-4262. Use ClientID and CallID from Rpc Client to detect retry requests #1436
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.
What changes were proposed in this pull request?
Use clientId and callID from the Client to uniquely identify the requests.
This will help in the case of retry requests.
(In this Jira, not changed default retry cache, the default is 1 minute using it same for now.)
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-4262
How was this patch tested?
Added one Integration test.
Able to get RetryCache and not able to acess methods like queryCache to check like whether retry(As this method is not public, for this we need to make a change in Ratis for that, so just tested this at OM level)