You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "haosdent (JIRA)" <ji...@apache.org> on 2015/11/03 07:12:27 UTC
[jira] [Updated] (MESOS-3822) Cannot specify multiple masters when
slave start up
[ https://issues.apache.org/jira/browse/MESOS-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
haosdent updated MESOS-3822:
----------------------------
Labels: docuentation (was: )
> Cannot specify multiple masters when slave start up
> ----------------------------------------------------
>
> Key: MESOS-3822
> URL: https://issues.apache.org/jira/browse/MESOS-3822
> Project: Mesos
> Issue Type: Bug
> Affects Versions: 0.26.0
> Reporter: Guangya Liu
> Labels: docuentation
> Fix For: 0.26.0
>
>
> This bug is reported from user list, the document should be updated by removing multiple masters when slave start up.
> /usr/sbin/mesos-slave --master=IP1:5050,IP2:5050,IP3:5050 …. --credential …
> Only if IP1 is the leader, the slave can register to master successfully, Or it will register fail.
> Slave log like this:
> Creating new client SASL connection
> Authentication timed out
> Failed to authenticate with master master@172.31.43.77:5050: Authentication discarded
> Authenticating with master master@172.31.43.77:5050
> Using default CRAM-MD5 authenticatee
> Is this a bug?Or it is designed like this.
> BTW: --master:zk://xxxxxxx work well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)