hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yuanbo Liu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-11716) Ozone: SCM: CLI: Revisit delete container API
Date Mon, 01 May 2017 05:29:04 GMT

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

Yuanbo Liu commented on HDFS-11716:

Because if a container is open and we try to delete without force option, that seems to work.

The default vaule of fource delete is false.

> Ozone: SCM: CLI: Revisit delete container API
> ---------------------------------------------
>                 Key: HDFS-11716
>                 URL: https://issues.apache.org/jira/browse/HDFS-11716
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: ozone
>            Reporter: Weiwei Yang
>            Assignee: Weiwei Yang
> Current delete container API seems can be possibly running into inconsistent state. SCM
maintains a mapping of container to nodes, datanode maintains the actual container's data.
When deletes a container, we need to make sure db is removed as well as the mapping in SCM
also gets updated. What if the datanode failed to remove stuff for a container, do we update
the mapping? We need to revisit the implementation and get these issues addressed. See more
discussion [here|https://issues.apache.org/jira/browse/HDFS-11675?focusedCommentId=15987798&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15987798].

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