[
https://issues.apache.org/jira/browse/KUDU-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16899412#comment-16899412
]
YifanZhang edited comment on KUDU-2914 at 8/3/19 8:35 AM:
----------------------------------------------------------
Thanks for explanations, I agree that for maintenance rereplicating all
replicas brings no benefits.
Thus this issue is very similar to KUDU-1827, my idea is making improvements
on rebalance tool to support batch migrating replicas from some specified
tservers to the others. But maybe this way isn't graceful enough for we call
'move_replica' many times, see KUDU-2246, it could be more reliable in certain
edge-case scenarios.
was (Author: zhangyifan27):
Thanks for explanations, I agree that for maintenance rereplicating all
replicas brings no benefits.
Thus this issue is similar to KUDU-1827.
> Rebalance tool support moving replicas from some specific tablet servers
> ------------------------------------------------------------------------
>
> Key: KUDU-2914
> URL: https://issues.apache.org/jira/browse/KUDU-2914
> Project: Kudu
> Issue Type: Improvement
> Components: CLI
> Reporter: YifanZhang
> Priority: Minor
>
> When we need to stop/upgrade some tablet servers in a kudu cluster, these
> tservers would become unavailable and tablets on these servers would be
> unhealthy in a period of time. In order to ensure the high availability of
> the cluster, it's better to move all replicas on these tservers to other
> tservers in a cluster, then stop or upgrade tservers. This can be achieved by
> rebalance tool to support specifying 'blacklist_tservers'.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
