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/07/03 15:17:00 UTC

[jira] [Updated] (HDDS-179) CloseContainer command should be executed only if all the prior "Write" type container requests get executed

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

Shashikant Banerjee updated HDDS-179:
-------------------------------------
    Attachment: HDDS-179.01.patch

> CloseContainer command should be executed only if all the  prior "Write" type container requests get executed
> -------------------------------------------------------------------------------------------------------------
>
>                 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
>
>
> 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 putKey, WriteChunk, DeleteKey, CompactChunk 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
(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