You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Grant Henke (JIRA)" <ji...@apache.org> on 2018/11/08 03:37:00 UTC

[jira] [Commented] (KUDU-2418) ksck should be able to auto-repair single replica tablets (with data loss)

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

Grant Henke commented on KUDU-2418:
-----------------------------------

Was this done in 1.8.0? I suspect a bad fix version. Will remove it. Feel free to correct it though.

> 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
>             Fix For: 1.8.0
>
>
> 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)