[
https://issues.apache.org/jira/browse/HDDS-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16582909#comment-16582909
]
Hudson commented on HDDS-179:
-----------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #14786 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/14786/])
HDDS-179. CloseContainer/PutKey command should be syncronized with write
(msingh: rev 5ef29087ad27f4f6b815dbc08ea7427d14df58e1)
* (add)
hadoop-ozone/integration-test/src/test/java/org/apache/hadoop/ozone/container/server/TestContainerStateMachine.java
* (edit)
hadoop-hdds/container-service/src/main/java/org/apache/hadoop/ozone/container/common/transport/server/ratis/ContainerStateMachine.java
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
