hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shashikant Banerjee (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDDS-450) Generate BlockCommitSequenceId in ContainerStateMachine for every commit operation in Ratis Leader
Date Mon, 08 Oct 2018 15:34:00 GMT

     [ https://issues.apache.org/jira/browse/HDDS-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Shashikant Banerjee updated HDDS-450:
-------------------------------------
    Attachment: HDDS-450.002.patch

> Generate BlockCommitSequenceId in ContainerStateMachine for every commit operation in
Ratis Leader
> --------------------------------------------------------------------------------------------------
>
>                 Key: HDDS-450
>                 URL: https://issues.apache.org/jira/browse/HDDS-450
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>          Components: Ozone Datanode
>            Reporter: Shashikant Banerjee
>            Assignee: Shashikant Banerjee
>            Priority: Major
>         Attachments: HDDS-450.001.patch, HDDS-450.002.patch
>
>
> BlockCommitSequenceId will be increasing long value generated in the Ratis leader for
every commit operation of a block and will be replicated over to the followers. This id will
be updated in OM and will be reported to SCM which will help the most consistent copy of a
open container replica in case the majority of the datanodes fail.
> The blockCommitSequenceId is same as the commit index of the flush(PUT_BLOCK) transaction
in Ratis.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message