[
https://issues.apache.org/jira/browse/KUDU-2604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17118772#comment-17118772
]
Grant Henke commented on KUDU-2604:
-----------------------------------
[~aserbin] Do you think the remaining functionality not addressed by location
awareness can/should be broken into new or smaller jiras? At a minimum I think
the subject needs to be updated to reflect the outstanding work given tservers
now have labels.
> Add label for tserver
> ---------------------
>
> Key: KUDU-2604
> URL: https://issues.apache.org/jira/browse/KUDU-2604
> Project: Kudu
> Issue Type: New Feature
> Reporter: Hong Shen
> Priority: Major
> Labels: location-awareness, rack-awareness
> Fix For: n/a
>
> Attachments: image-2018-10-15-21-52-21-426.png
>
>
> When the cluster is bigger and bigger, big table with a lot of tablets will
> be distributed in almost all the tservers, when client write batch to the big
> table, it may cache connections to lots of tservers, the scalability may
> constrained.
> If the tablets in one table or partition only in a part of tservers, client
> will only have to cache connections to the part's tservers. So we propose to
> add label to tservers, each tserver belongs to a unique label. Client
> specified label when create table or add partition, the tablets will only be
> created on the tservers in specified label, if not specified, defalut label
> will be used.
> It will also benefit for:
> 1 Tserver across data center.
> 2 Heterogeneous tserver, like different disk, cpu or memory.
> 3 Physical isolating, especially IO, isolate some tables with others.
> 4 Gated Launch, upgrade tservers one by one label.
> In our product cluster, we have encounter the above issues and need to be
> resolved.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
