[
https://issues.apache.org/jira/browse/HDDS-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16772597#comment-16772597
]
Shashikant Banerjee commented on HDDS-1086:
-------------------------------------------
Thanks [~hanishakoneru]. In the case mentioned, we always let the ozone client
aware of who the leader is in case a request gets redirected to a different OM
Server so that next request it can send to a raft Client on OM1.
If Ozone Client is only sending requests to OM2 and OM2 is not the leader, it
will fail and the redirection still needs to happen to OM1 in such cases.
> Remove RaftClient from OM
> -------------------------
>
> Key: HDDS-1086
> URL: https://issues.apache.org/jira/browse/HDDS-1086
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Components: HA, OM
> Reporter: Hanisha Koneru
> Assignee: Hanisha Koneru
> Priority: Major
> Attachments: HDDS-1086.001.patch
>
>
> Currently we run RaftClient in OM which takes the incoming client requests
> and submits it to the OM's Ratis server. This hop can be avoided if OM
> submits the incoming client request directly to its Ratis server.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
