You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Mike Percy (JIRA)" <ji...@apache.org> on 2017/12/20 00:59:13 UTC

[jira] [Created] (KUDU-2246) Make "kudu tablet change_config move_replica" more reliable

Mike Percy created KUDU-2246:
--------------------------------

             Summary: Make "kudu tablet change_config move_replica" more reliable
                 Key: KUDU-2246
                 URL: https://issues.apache.org/jira/browse/KUDU-2246
             Project: Kudu
          Issue Type: Improvement
          Components: consensus, ops-tooling
            Reporter: Mike Percy


As part of KUDU-1097 we changed the replica move tool to use the new 3-4-3 re-replication scheme when it's enabled. In certain edge-case scenarios, such as when there is a replica failure in the middle of a move operation, the reliability of the tool may be reduced, and the node slated for removal may not be removed. This is especially true if the user hits ctrl+c and kills the tool before the movement process is complete in the context of a simultaneous failure.

We can improve this by implementing leadership transfer (KUDU-2245) and having a leader gracefully step down when there is a suitable replacement and the leader is marked with the "replace=true" attribute in the Raft config.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)