You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Grant Henke (Jira)" <ji...@apache.org> on 2020/06/03 15:34:00 UTC

[jira] [Updated] (KUDU-3115) Improve scalability of Kudu masters

     [ https://issues.apache.org/jira/browse/KUDU-3115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Grant Henke updated KUDU-3115:
------------------------------
    Component/s: master

> Improve scalability of Kudu masters
> -----------------------------------
>
>                 Key: KUDU-3115
>                 URL: https://issues.apache.org/jira/browse/KUDU-3115
>             Project: Kudu
>          Issue Type: Improvement
>          Components: master
>            Reporter: Alexey Serbin
>            Priority: Major
>
> Currently, multiple masters in a multi-master Kudu cluster are used only for high availability & fault tolerance use cases, but not for sharing the load among the available master nodes.  For example, Kudu clients detect current leader master upon connecting to the cluster and send all their subsequent requests to the leader master, so serving many more clients require running masters on more powerful nodes.  Current design assumes that masters store and process the requests for metadata only, but that makes sense only up to some limit on the rate of incoming client requests.
> It would be great to achieve better 'horizontal' scalability for Kudu masters.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)