[
https://issues.apache.org/jira/browse/KUDU-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17735550#comment-17735550
]
Mahesh Reddy edited comment on KUDU-3476 at 6/29/23 8:29 PM:
-------------------------------------------------------------
Design doc for this feature:
https://docs.google.com/document/d/1r-p0GW8lj2iLA3VGvZWAem09ykCmR5jEe8npUhJ07G8/edit?usp=sharing
was (Author: mreddy):
Design doc for this feature:
[https://docs.google.com/document/d/1EwL1sZnXXT94pLTQpfmxC59E29wXM2JeJdc-HC7XGSY/edit?usp=sharing|https://docs.google.com/document/d/1r-p0GW8lj2iLA3VGvZWAem09ykCmR5jEe8npUhJ07G8/edit]
> Make replica placement range and table aware
> --------------------------------------------
>
> Key: KUDU-3476
> URL: https://issues.apache.org/jira/browse/KUDU-3476
> Project: Kudu
> Issue Type: New Feature
> Components: master, tserver
> Reporter: Mahesh Reddy
> Assignee: Mahesh Reddy
> Priority: Major
>
> The current replica placement algorithm uses the power of two choices
> algorithm. This algorithm randomly selects tservers and places the replica on
> the tserver with less replicas. This can lead to potential hotspotting as it
> doesn't discriminate by range or table so many tablets from the same
> range/table can be disproportionally distributed.
> With this new feature, the replicas will be placed in a way that the tablets
> per range will be equally distributed amongst the available tservers. If
> multiple tservers have the same amount of replicas per range, then the
> tserver with less replicas for that table will be selected. If multiple
> tservers have the same amount of replicas for that table, the tserver with
> less total replicas will be chosen.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
