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

Neil Conway updated MESOS-3592:
-------------------------------
    Description: 
Per the HA docs, whether an instance of {{mesos-slave}} is running in "HA mode" 
depends on whether the slave uses {{\-\-master=zk://host:port/path}}, rather 
than the non-HA form {{\-\-master=host:port}}. However, if a master is started 
in HA mode (connected to Zk) but a slave is started with the latter syntax, we 
don't issue a warning.

1. Is this a sensible configuration? I can't think of a reason why you'd 
configure Mesos like this, but maybe one exists.
2. If not, should we have the slave emit a warning or error message?

  was:
Per the HA docs, whether an instance of {{mesos-slave}} is running in "HA mode" 
depends on whether the slave uses {{--master=zk://host:port/path}}, rather than 
the non-HA form {{--master=host:port}}. However, if a master is started in HA 
mode (connected to Zk) but a slave is started with the latter syntax, we don't 
issue a warning.

1. Is this a sensible configuration? I can't think of a reason why you'd 
configure Mesos like this, but maybe one exists.
2. If not, should we have the slave emit a warning or error message?


> Consider warning when non-Zk slave connects to Zk master
> --------------------------------------------------------
>
>                 Key: MESOS-3592
>                 URL: https://issues.apache.org/jira/browse/MESOS-3592
>             Project: Mesos
>          Issue Type: Bug
>          Components: slave
>            Reporter: Neil Conway
>              Labels: mesosphere
>
> Per the HA docs, whether an instance of {{mesos-slave}} is running in "HA 
> mode" depends on whether the slave uses {{\-\-master=zk://host:port/path}}, 
> rather than the non-HA form {{\-\-master=host:port}}. However, if a master is 
> started in HA mode (connected to Zk) but a slave is started with the latter 
> syntax, we don't issue a warning.
> 1. Is this a sensible configuration? I can't think of a reason why you'd 
> configure Mesos like this, but maybe one exists.
> 2. If not, should we have the slave emit a warning or error message?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to