[
https://issues.apache.org/jira/browse/KUDU-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Serbin resolved KUDU-2823.
---------------------------------
Resolution: Fixed
Fix Version/s: 1.11.0
[~oclarms] implemented a new placement option for replicas of newly added
tablets in {{32cbf9d6bf37ee2df21837e0f62bd15064b1b4ed}}. Now, specifying a
dimension label for a new table or a new partition, it's possible to place new
replicas evenly spread within a Kudu cluster while counting only replicas with
the specified label, not just the total count of replicas as it was prior to
the mentioned changelist. That helps to avoid hotspotting of recently added
tablet servers if adding many new partitions for the same range in a cluster
that hasn't been rebalanced (e.g., using {{kudu cluster rebalance}} CLI) after
new tablet servers were added.
> Place tablet replicas based on dimension
> ----------------------------------------
>
> Key: KUDU-2823
> URL: https://issues.apache.org/jira/browse/KUDU-2823
> Project: Kudu
> Issue Type: Improvement
> Reporter: HeLifu
> Assignee: Xu Yao
> Priority: Major
> Fix For: 1.11.0
>
>
> 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.14#76016)
