[jira] [Assigned] (KUDU-2200) Sanity-check that users specify the right number of masters when connecting

["Todd Lipcon (JIRA)" <ji...@apache.org>]

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

Todd Lipcon reassigned KUDU-2200:
---------------------------------

    Assignee: Todd Lipcon

> Sanity-check that users specify the right number of masters when connecting
> ---------------------------------------------------------------------------
>
>                 Key: KUDU-2200
>                 URL: https://issues.apache.org/jira/browse/KUDU-2200
>             Project: Kudu
>          Issue Type: Improvement
>          Components: client, master, supportability
>    Affects Versions: 1.6.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>
> A common issue I've seen is that users set up an HA master setup (3 masters) but then in various cases only specify one of the masters when they try to connect using the client. This currently will work if it happens that they picked the leader master, and otherwise will return a s omewhat confusing "no leader" error message.
> We should improve usability here by having the master send back a list of the master addresses in  the case that it isn't the leader,  and the client can use this to provide a more actionable error message like "Client connection specified only a subset of the cluster's masters" or somesuch.
> I wouldn't want to  automatically reconfigure the client and reconnect because this puts the client in a configuration state that will fail once the one master they specified goes down.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)