[HDDS-5051] Ensure failover to suggested leader if any for NotLeaderException

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.2.0
• Component/s: SCM HA
• Labels: pull-request-available
• Assignee: Shashikant Banerjee
• Reporter: Shashikant Banerjee
• Created: 31/Mar/21 09:04
• Updated: 13/Dec/24 09:56
• Resolved: 26/Apr/21 11:20

Description

Currently, ratis suggested leader info is not propagated to rpc clients for ratis request failures. Idea here is to propagate this info and perform failover accordingly if request fail with NotLeaderException.

Issue Links

• fixes: HDDS-4281 Use suggestedLeader for SCM failover proxy performing failover
• is duplicated by: HDDS-3189 Revisit SCM client retry and failover when SCM leader changes
• is duplicated by: HDDS-4281 Use suggestedLeader for SCM failover proxy performing failover
• is duplicated by: HDDS-4545 FailoverProxyProvider of SCM client should support leaderHint.
• is related to: HDDS-3334 OM Client failover to next OM on NotLeaderException
• is related to: HDDS-3936 OM client failover ignores suggested leader info
• links to: GitHub Pull Request #2141