[
https://issues.apache.org/jira/browse/KUDU-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16838599#comment-16838599
]
Grant Henke commented on KUDU-2823:
-----------------------------------
{quote}
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.
{quote}
It sounds like a change to improve placement policies could solve the need to
rebalance immediately. Was that considered as an option?
{quote}
Balance according to the number of tablets in the same range partition, not the
number of tablets on tserver
{quote}
I do not totally understand the motivation for this. Is this an effort to
improve throughput on a hot partition? Would a user always want this to be
used/enabled?
> 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)
