[jira] [Commented] (KUDU-1330) Add tool to unsafely recover from loss of majority (or all) tablet replicas

["Dinesh Bhat (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KUDU-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15812822#comment-15812822 ] 

Dinesh Bhat commented on KUDU-1330:
-----------------------------------

I wasn't earlier Todd, I am planning to work on this, it looks like this requires KUDU-1721 to be resolved first.

> Add tool to unsafely recover from loss of majority (or all) tablet replicas
> ---------------------------------------------------------------------------
>
>                 Key: KUDU-1330
>                 URL: https://issues.apache.org/jira/browse/KUDU-1330
>             Project: Kudu
>          Issue Type: New Feature
>          Components: ops-tooling
>    Affects Versions: 0.7.0
>            Reporter: Todd Lipcon
>            Assignee: Dinesh Bhat
>
> [~bruceSz] ran into this issue: if you have a table with replication set to 1, and you permanently lose a node, the table is stuck in a bad state. It would be nice to allow the operator to accept the data loss and replace the lost tablet with a new (empty) one.
> Similarly, I've had a few people ask about the scenario where you lose 2 of 3 replicas and you are willing to accept data loss, and force recovery from the remaining one replica.
> We should add a tool (or tools) for these recovery scenarios.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)