You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Shashikant Banerjee (JIRA)" <ji...@apache.org> on 2018/11/06 14:29:00 UTC

[jira] [Commented] (HDDS-709) Modify Close Container handling sequence on datanodes

    [ https://issues.apache.org/jira/browse/HDDS-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16676823#comment-16676823 ] 

Shashikant Banerjee commented on HDDS-709:
------------------------------------------

Patch v1 blocks on RATIS-394.

> Modify Close Container handling sequence on datanodes
> -----------------------------------------------------
>
>                 Key: HDDS-709
>                 URL: https://issues.apache.org/jira/browse/HDDS-709
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>          Components: Ozone Datanode
>            Reporter: Shashikant Banerjee
>            Assignee: Shashikant Banerjee
>            Priority: Major
>         Attachments: HDDS-709.000.patch, HDDS-709.001.patch
>
>
> With quasi closed container state for handling majority node failures, the close container handling sequence in Datanodes need to change. Once the datanodes receive a close container command from SCM, the open container replicas individually be marked in the closing state. In a closing state, only the transactions coming from the Ratis leaderĀ  are allowed , all other write transaction will fail. A close container transaction will be queued via Ratis on the leader which will be replayed to the followers which makes it transition to CLOSED/QUASI CLOSED state.



--
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