[
https://issues.apache.org/jira/browse/HDDS-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16771589#comment-16771589
]
Shashikant Banerjee commented on HDDS-1086:
-------------------------------------------
Thanks [~hanishakoneru] for reporting this. I have one question here:
1) RaftClient has many useful features like, async API, asynchronous retries,
ordering the request in the client side by maintaining a sliding window so that
it never serves requests out of order etc. With all these features built in,
removing Raft Client here may lead to handle some of these cases in Ozone.
The alternative approach would be to implement Short Circuit read/write in
Ratis itself to address the concern here. What do you think?
> 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]
