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-709) Modify Close Container handling sequence on datanodes
Date Fri, 09 Nov 2018 23:53:00 GMT

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

Shashikant Banerjee updated HDDS-709:
-------------------------------------
    Attachment: HDDS-709.005.patch

> 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, HDDS-709.002.patch, HDDS-709.003.patch,
HDDS-709.004.patch, HDDS-709.005.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


Mime
View raw message