[
https://issues.apache.org/jira/browse/KUDU-2418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Henke updated KUDU-2418:
------------------------------
Fix Version/s: (was: 1.8.0)
> ksck should be able to auto-repair single replica tablets (with data loss)
> --------------------------------------------------------------------------
>
> Key: KUDU-2418
> URL: https://issues.apache.org/jira/browse/KUDU-2418
> Project: Kudu
> Issue Type: New Feature
> Components: ksck
> Affects Versions: 1.7.0
> Reporter: Adar Dembo
> Priority: Major
>
> There's an established Kudu workflow for manually "repairing" a tablet that
> has only one working replica, using the unsafe_config_change CLI tool. I used
> quotes around repairing because while it brings the tablet back to a healthy
> state as far as Kudu is concerned, the tablet may have suffered data loss. In
> some circumstances, however, that's something users are willing to accept.
> The problem is when this happens writ large, to an entire cluster. For
> example, suppose a three node cluster hosting 1000 tablets loses two nodes.
> It should be possible to automate this repair process so that users needn't
> script it themselves.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
