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 14:49:00 UTC

[jira] [Updated] (KUDU-2778) Explore limitations of multi-master Kudu deployments with more than 3 masters

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

Grant Henke updated KUDU-2778:
------------------------------
    Labels: roadmap-candidate supportability  (was: )

> Explore limitations of multi-master Kudu deployments with more than 3 masters
> -----------------------------------------------------------------------------
>
>                 Key: KUDU-2778
>                 URL: https://issues.apache.org/jira/browse/KUDU-2778
>             Project: Kudu
>          Issue Type: Task
>          Components: master
>            Reporter: Alexey Serbin
>            Priority: Major
>              Labels: roadmap-candidate, supportability
>
> Currently, the recommended limit of Kudu masters in multi-master deployment is 3 (i.e. no more than 3 masters is recommended): https://github.com/apache/kudu/blob/branch-1.9.x/docs/known_issues.adoc#scale
> It would be nice to clarify whether there is anything substantial behind that limit.  As of now the recommendation stems from the fact that all of our multi-master tests and tested deployments use 3 masters.  Overall, being able to deploy 5 or more masters in case of bigger clusters makes sense from the HA perspective.



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