[
https://issues.apache.org/jira/browse/KUDU-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon resolved KUDU-1330.
-------------------------------
Resolution: Fixed
Fix Version/s: 1.4.0
Target Version/s: (was: 1.5.0)
> 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
> Priority: Major
> Fix For: 1.4.0
>
>
> [~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
(v7.6.3#76005)
