hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mukul Kumar Singh (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDDS-179) CloseContainer/PutKey command should be syncronized with write operations.
Date Thu, 16 Aug 2018 18:17:00 GMT

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

Mukul Kumar Singh updated HDDS-179:
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Thanks for the contribution [~shashikant]. I have committed this to trunk.

> CloseContainer/PutKey command should be syncronized with write operations.
> --------------------------------------------------------------------------
>                 Key: HDDS-179
>                 URL: https://issues.apache.org/jira/browse/HDDS-179
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>          Components: Ozone Client, Ozone Datanode
>            Reporter: Shashikant Banerjee
>            Assignee: Shashikant Banerjee
>            Priority: Major
>             Fix For: 0.2.1
>         Attachments: HDDS-179.01.patch, HDDS-179.02.patch, HDDS-179.03.patch, HDDS-179.04.patch,
HDDS-179.05.patch, HDDS-179.06.patch, HDDS-179.07.patch, HDDS-179.08.patch, HDDS-179.09,patch,
HDDS-179.10.patch, HDDS-179.11.patch, HDDS-179.12.patch
> When a close Container command request comes to a Datanode (via SCM hearbeat response)
through the Ratis protocol, all the prior enqueued "Write" type of request like  WriteChunk
etc should be executed first before CloseContainer request gets executed. This synchronization
needs to be handled in the containerStateMachine. 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