[
https://issues.apache.org/jira/browse/KUDU-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15606212#comment-15606212
]
Dinesh Bhat commented on KUDU-1618:
-----------------------------------
Thanks [~tlipcon], agreed to your points above that this is not a bug. I
confirmed that ksck as of now doesn't know about this spurious replica
resulting from the tool's action. I wonder if it's even possible to show this
info via ksck because I guess these reports are not sent to master ?
> Add local_replica tool to delete a replica
> ------------------------------------------
>
> Key: KUDU-1618
> URL: https://issues.apache.org/jira/browse/KUDU-1618
> Project: Kudu
> Issue Type: Improvement
> Components: ops-tooling
> Affects Versions: 1.0.0
> Reporter: Todd Lipcon
> Assignee: Dinesh Bhat
>
> Occasionally we've hit cases where a tablet is corrupt in such a way that the
> tserver fails to start or crashes soon after starting. Typically we'd prefer
> the tablet just get marked FAILED but in the worst case it causes the whole
> tserver to fail.
> For these cases we should add a 'local_replica' subtool to fully remove a
> local tablet. Related, it might be useful to have a 'local_replica archive'
> which would create a tarball from the data in this tablet for later
> examination by developers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
