[
https://issues.apache.org/jira/browse/HDFS-11675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15988042#comment-15988042
]
Weiwei Yang commented on HDFS-11675:
------------------------------------
Thanks [~vagarychen] and [~anu] for your quick responses.
[~anu], I just uploaded v3 patch to address your 1st and 2nd comment. Regarding
to your 3rd comment, actually I found the same thing while doing this task. SCM
doesn't remove the container from its db so it might get to an inconsistent
state, I have created HDFS-11716 to revisit the implementation and make sure
those doubts (including the force tag) can be addressed. The purpose of this
jira is to support delete container from command line, so lets keep its scope
constrained, doesn't that sound good to you? Thanks.
> Ozone: SCM CLI: Implement delete container command
> --------------------------------------------------
>
> Key: HDFS-11675
> URL: https://issues.apache.org/jira/browse/HDFS-11675
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ozone
> Reporter: Weiwei Yang
> Assignee: Weiwei Yang
> Labels: command-line
> Attachments: HDFS-11675-HDFS-7240.001.patch,
> HDFS-11675-HDFS-7240.002.patch, HDFS-11675-HDFS-7240.003.patch
>
>
> Implement delete container
> {code}
> hdfs scm -container del <container name> -f
> {code}
> Deletes a container if it is empty. The -f options can be used to force a
> delete of a non-empty container. If container name specified not exist,
> prints a clear error message.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
