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] [Updated] (HDDS-1029) Allow option for force in DeleteContainerCommand
Date Mon, 04 Feb 2019 04:06:00 GMT

     [ https://issues.apache.org/jira/browse/HDDS-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Bharat Viswanadham updated HDDS-1029:
    Attachment: HDDS-1029.05.patch

> 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, HDDS-1029.05.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

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

View raw message