[ https://issues.apache.org/jira/browse/HDDS-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hanisha Koneru updated HDDS-1072: --------------------------------- Attachment: HDDS-1072.001.patch > Propagate OM Ratis NotLeaderException to Client > ----------------------------------------------- > > Key: HDDS-1072 > URL: https://issues.apache.org/jira/browse/HDDS-1072 > Project: Hadoop Distributed Data Store > Issue Type: Sub-task > Components: OM > Reporter: Hanisha Koneru > Assignee: Hanisha Koneru > Priority: Major > Attachments: HDDS-1072.001.patch > > > When OM Ratis Client receives a response from the Ratis server for its > request, it also gets the LeaderId of server which processed this request > (the current Leader OM nodeId). This information should be propagated to the > RPC client. The RPC client should send subsequent requests to the Ratis > Client on the Leader OM. This helps avoid an extra hop from Follower OM Ratis > Client to Leader OM Ratis server for every request. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org