[
https://issues.apache.org/jira/browse/HDDS-4533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17241358#comment-17241358
]
Glen Geng commented on HDDS-4533:
---------------------------------
RaftClientRequest can serve both read request and write request, and provide
linearizability. Given a read request, the RaftServer will throw out a
NotLeaderException if it has not replayed all the log entries.
Since in our case, the read request does not go though raft, we have to
manually do the isLeaderReady check.
> Avoid rewriting pipeline information during PipelineStateManagerV2Impl
> initialization
> -------------------------------------------------------------------------------------
>
> Key: HDDS-4533
> URL: https://issues.apache.org/jira/browse/HDDS-4533
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Components: SCM HA
> Reporter: Nanda kumar
> Priority: Major
> Labels: newbie
>
> {{PipelineStateManagerV2Impl}} adds the pipeline back to the pipeline table
> (RocksDB) during initialization which is unnecessary. This can be avoided.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
