You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Yiqun Lin (JIRA)" <ji...@apache.org> on 2019/02/01 06:31:00 UTC
[jira] [Commented] (HDDS-1029) Allow option for force in
DeleteContainerCommand
[ https://issues.apache.org/jira/browse/HDDS-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16758018#comment-16758018 ]
Yiqun Lin commented on HDDS-1029:
---------------------------------
Before the check, can we check is the container is replicated across three nodes? I mean that the container maybe not replicated successfully in hddsDatanodeService1 sometimes. Then causes the failure.
Also another way, can we refactor this, use {{STAND_ALONE}} type with {{ONE}} factor way: one deletion bahaviour for open state container and the other one for un-open container.
> Allow option for force in DeleteContainerCommand
> ------------------------------------------------
>
> Key: HDDS-1029
> URL: https://issues.apache.org/jira/browse/HDDS-1029
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Reporter: Bharat Viswanadham
> Assignee: Bharat Viswanadham
> Priority: Major
> Labels: pull-request-available
> Attachments: HDDS-1029.00.patch, HDDS-1029.01.patch, HDDS-1029.02.patch, HDDS-1029.03.patch, HDDS-1029.04.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Right now, we check container state if it is not open, and then we delete container.
> We need a way to delete the containers which are open, so adding a force flag will allow deleting a container without any state checks. (This is required for delete replica's when SCM detects over-replicated, and that container to delete can be in open state)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org