[
https://issues.apache.org/jira/browse/HDDS-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16573841#comment-16573841
]
Hanisha Koneru commented on HDDS-267:
-------------------------------------
Thanks [~arpitagarwal] and [~bharatviswa] for reviews.
I have updated patch v05 to handle the create and update container file cases
separately. Thanks Bharat for catching it.
> Handle consistency issues during container update/close
> -------------------------------------------------------
>
> Key: HDDS-267
> URL: https://issues.apache.org/jira/browse/HDDS-267
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Reporter: Hanisha Koneru
> Assignee: Hanisha Koneru
> Priority: Major
> Fix For: 0.2.1
>
> Attachments: HDDS-267.001.patch, HDDS-267.002.patch,
> HDDS-267.003.patch, HDDS-267.004.patch, HDDS-267.005.patch
>
>
> During container update and close, the .container file on disk is modified.
> We should make sure that the in-memory state and the on-disk state for a
> container are consistent.
> A write lock is obtained before updating the container data during close or
> update operations.
> During update operation, if the on-disk update of .container file fails, then
> the container metadata is in-memory is also reset to the old value.
> During close operation, if the on-disk update of .container file fails, then
> the in-memory containerState is set to CLOSING so that no new operations are
> permitted.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
