[HDDS-2311] Fix logic of RetryPolicy in OzoneClientSideTranslatorPB

• Type: Sub-task
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 0.5.0
• Component/s: OM HA, Ozone Manager
• Labels: pull-request-available
• Target Version/s: 0.5.0
• Assignee: Hanisha Koneru
• Reporter: Bharat Viswanadham
• Created: 15/Oct/19 21:57
• Updated: 04/Jun/20 20:16
• Resolved: 01/Nov/19 04:41

Description

OzoneManagerProtocolClientSideTranslatorPB.java

L251: if (cause instanceof NotLeaderException)

{ NotLeaderException notLeaderException = (NotLeaderException) cause; omFailoverProxyProvider.performFailoverIfRequired( notLeaderException.getSuggestedLeaderNodeId()); return getRetryAction(RetryAction.RETRY, retries, failovers); }

 

The suggested leader returned from Server is not used during failOver, as the cause is a type of RemoteException. So with current code, it does not use suggested leader for failOver at all and by default with each OM, it tries max retries.

 

Issue Links

• links to: GitHub Pull Request #51