[jira] [Updated] (KUDU-2331) Use tablet_id filter for 'move_replica' while running ksck-based pre-flight consistency check

["Will Berkeley (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KUDU-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Will Berkeley updated KUDU-2331:
--------------------------------
    Code Review: http://gerrit.cloudera.org:8080/9510

Actually, the tool does use tablet id filters. The problem is that it insists all tservers be up to pass the pre-flight check. This is too restrictive.

> Use tablet_id filter for 'move_replica' while running ksck-based pre-flight consistency check
> ---------------------------------------------------------------------------------------------
>
>                 Key: KUDU-2331
>                 URL: https://issues.apache.org/jira/browse/KUDU-2331
>             Project: Kudu
>          Issue Type: Improvement
>          Components: ksck, supportability
>            Reporter: Alexey Serbin
>            Assignee: Will Berkeley
>            Priority: Major
>
> {\{kudu tablet change_config move_replica}} could use {{tablet_id}} filter to perform pre-flight consistency check.  Right now, it always fails with {{Network error: ksck pre-move health check failed: Not all Tablet Servers are reachable}} error when whatever a tserver in the cluster is dead.  No matter if the dead server is not involved in serving a replica of the tablet, the command doesn't allow users to run it.
> The tool should allow moving a tablet replica when the destination server and all tablet replicas are alive.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)