hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bharat Viswanadham (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDDS-267) Handle consistency issues during container update/close
Date Fri, 03 Aug 2018 22:52:00 GMT

    [ https://issues.apache.org/jira/browse/HDDS-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16568883#comment-16568883

Bharat Viswanadham commented on HDDS-267:

Hi [~hanishakoneru]

Patch is not applying on top of trunk. Sorry, missed reviewing these changes. It needs to

> 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
> 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

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message