[
https://issues.apache.org/jira/browse/HDDS-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16773397#comment-16773397
]
Hanisha Koneru commented on HDDS-1086:
--------------------------------------
Thank you [~shashikant] for the discussion.
If we get the current LeaderId as part of RaftClientReply, we can use that to
redirect subsequent requests from RPC client to RaftClient on Leader OM. So
agreed, we can keep the RaftClient and utilize its features. I am resolving
this Jira as 'Not a Problem'.
> 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]
