[
https://issues.apache.org/jira/browse/KUDU-2200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17155691#comment-17155691
]
Bankim Bhavsar commented on KUDU-2200:
--------------------------------------
Noting the commit:
https://github.com/apache/kudu/commit/3e86797e6e73365c26b8826083c447494c7fa7eb
> 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
> Priority: Major
> Fix For: 1.6.0
>
>
> 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
(v8.3.4#803005)
