[
https://issues.apache.org/jira/browse/HDDS-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16551612#comment-16551612
]
Shashikant Banerjee edited comment on HDDS-181 at 7/21/18 10:42 AM:
--------------------------------------------------------------------
patch v7 fixes a bug in "handleWriteChunk" in KeyValueHandler where we need to
update the openContainerBlockMap only while WRITE_DATA stage not during
COMMIT_DATA phase as it will lead to duplicating the chunkInfo in the
openContainerBlockMap.
Failed tests are not related. They work on my local machine.
was (Author: shashikant):
patch v7 fixes a bug in "handleWriteChunk" in KeyValueHandler where we need to
update the openContainerBlockMap only while WRITE_DATA stage not during
COMMIT_DATA phase as it will lead to duplicating the chunkInfo in the
openContainerBlockMap.
> CloseContainer should commit all pending open Keys on a datanode
> ----------------------------------------------------------------
>
> 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, HDDS-181.03.patch,
> HDDS-181.04.patch, HDDS-181.05.patch, HDDS-181.06.patch, HDDS-181.07.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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
