[
https://issues.apache.org/jira/browse/KUDU-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16840359#comment-16840359
]
Grant Henke commented on KUDU-2823:
-----------------------------------
I think the solution for that problem would be tablet leader balancing which
ensures the leaders (the tablet servers the receive writes) are balanced across
the cluster. We don't currently have support for that, but it is listed as a
goal in KUDU-886.
I agree, given how common using time in range partitions is, that it would be
useful not only to spread leaders across a cluster, but to spread the leaders
of a given range partition evenly too. It could be 3 tiered goals; balance
range leaders, balance table leaders, balance cluster leaders.
Perhaps [~wdberkeley] has some thoughts.
> Rebalance range partition
> -------------------------
>
> Key: KUDU-2823
> URL: https://issues.apache.org/jira/browse/KUDU-2823
> Project: Kudu
> Issue Type: Improvement
> Reporter: HeLifu
> Assignee: Xu Yao
> Priority: Major
>
> Right now we will add new range every day for a fact table which has
> range+hash partitions, and then rebalance it as soon as possible. It seems
> that not only the new added tablets of this table but also the historical
> tablets will be rebalanced. But the historical tablets already have data, so
> they are heavy to move and it will increase the disk and network suddenly.
> So, I think it will be good to rebalance the new added range partitions.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
