You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kudu.apache.org by "Mike Percy (JIRA)" <ji...@apache.org> on 2018/02/16 23:21:00 UTC

[jira] [Resolved] (KUDU-2304) Add TABLET_DATA_DELETED option to kudu remote_replica delete

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

Mike Percy resolved KUDU-2304.
------------------------------
       Resolution: Won't Fix
    Fix Version/s: n/a

Closing this in favor of KUDU-2311 which is less awkward to implement but also addresses the use case I had in mind for this change to the tool.

> Add TABLET_DATA_DELETED option to kudu remote_replica delete
> ------------------------------------------------------------
>
>                 Key: KUDU-2304
>                 URL: https://issues.apache.org/jira/browse/KUDU-2304
>             Project: Kudu
>          Issue Type: Improvement
>          Components: ops-tooling
>    Affects Versions: 1.6.0
>            Reporter: Mike Percy
>            Priority: Major
>             Fix For: n/a
>
>
> The remote_replica delete tool should have the option to delete a replica in "unsafe clean" mode in addition to the default of tombstoning, just like the local_replica delete command. This is useful in certain recovery scenarios, such as when the consensus metadata file is corrupted.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)