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-181) CloseContainer should commit all pending open Keys on a dataode
Date Tue, 10 Jul 2018 10:21:00 GMT

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

Shashikant Banerjee updated HDDS-181:
    Status: Patch Available  (was: Open)

> CloseContainer should commit all pending open Keys on a dataode
> ---------------------------------------------------------------
>                 Key: HDDS-181
>                 URL: https://issues.apache.org/jira/browse/HDDS-181
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>          Components: Ozone Datanode
>            Reporter: Shashikant Banerjee
>            Assignee: Shashikant Banerjee
>            Priority: Major
>             Fix For: 0.2.1
>         Attachments: HDDS-181.01.patch, HDDS-181.02.patch
> A close container command arrives in the Datanode by the SCM heartBeat response.It will
then be queued up over the ratis pipeline. Once the command execution starts inside the Datanode,
it will mark the container in CLOSING State. All the pending open keys for the container now
will be committed followed by the transition of the container state from CLOSING to CLOSED.
For achieving this, all the open keys for a container need to be tracked.
> This Jira aims to address this.

This message was sent by Atlassian JIRA

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

View raw message