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

• Type: New Feature
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.7.0
• Component/s: ksck
• Assignee: Unassigned
• Reporter: Adar Dembo
• Created: 27/Apr/18 03:22
• Updated: 08/Nov/18 18:59

Description

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.

Issue Links

• relates to: KUDU-2410 Add auto-repair function to ksck to repair "stuck tablet" situations common on older versions