Repository navigation
Conversation
…ption returned by SCM Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Generated-by: Claude Code (Opus 5.5)
What changes were proposed in this pull request?
SCM converts errors that should be retried on the same SCM (Ratis
LeaderNotReadyException,ReconfigurationInProgressException,ReconfigurationTimeoutException,ResourceUnavailableException, and some certificate failures) toRetriableWithNoFailoverException. The SCM client checks for it inSCMHAUtils.checkRetriableWithNoFailoverException, using the exception unwrapped fromRemoteException. ButRetriableWithNoFailoverExceptionhas noStringconstructor, soRemoteException.unwrapRemoteException()cannot create it and returns theRemoteExceptionitself. The check never matches, and the client fails over to another SCM instead of retrying the same one.This change also matches the class name of the
RemoteException, so the client retries the same SCM (up to the configured retry count) as intended.What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-17320
How was this patch tested?
Added
TestSCMHAUtils#retriesSameScmOnRetriableWithNoFailoverException, which fails without the fix. ExistingTestSCMFailoverProxyProvider*tests pass.🤖 Generated with Claude Code