[
https://issues.apache.org/jira/browse/HDDS-4533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17242031#comment-17242031
]
Glen Geng edited comment on HDDS-4533 at 12/2/20, 4:42 AM:
-----------------------------------------------------------
The rocksDB could be considered as a snapshot of SCM, as long as we add the
applyIndex into the DB.
The initialize job is actually loadSnapshot. After it is done,
StateMachineUpdater needs to replay the entries between appyIndex + 1 and
lastLogIndex to restore the states of SCM. Finally, the leader SCM can process
incoming read/write request.
was (Author: glengeng):
The rocksDB could be considered as a snapshot of SCM, as long as we add the
applyIndex into the DB.
The initialize job is actually loadSnapshot. After it is done,
StateMachineUpdater needs replaying entries between appyIndex + 1 and
lastLogIndex. Finally, the leader SCM can process incoming read/write request.
> 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]
