Ah, now I get it.
And this comports with the behavior I am observing right now.
Thanks again, Jie.
-Paul
> On Nov 13, 2015, at 5:55 PM, Jie Yu wrote:
>
> Paul, the slave will terminate after receiving a Shutdown message. The slave
> will be restarted (e.g., by monit or systemd) and register
Paul, the slave will terminate after receiving a Shutdown message. The
slave will be restarted (e.g., by monit or systemd) and register with the
master as a new slave (a different slaveId).
- Jie
On Fri, Nov 13, 2015 at 2:53 PM, Paul wrote:
> Jie,
>
> Thank you.
>
> That's odd behavior, no? Tha
Jie,
Thank you.
That's odd behavior, no? That would seem to mean that the slave can never again
join the cluster, at least not from it's original IP@.
What if the master bounces? Will it then tolerate the slave?
-Paul
On Nov 13, 2015, at 4:46 PM, Jie Yu wrote:
>> Can that slave never again
>
> Can that slave never again be added into the cluster, i.e., what happens
> if it comes up 1 second after exceeding the timeout product?
It'll not be added to the cluster. The master will send a Shutdown message
to the slave if it comes up after the timeout.
- Jie
On Fri, Nov 13, 2015 at 1:4
Hi All,
IIRC, after (max_slave_ping_timeouts * slave_ping_timeout) is exceeded
without a response from a mesos-slave, the master will remove the slave. In
the Mesos UI I can see slave state transition from 1 deactivated to 0.
Can that slave never again be added into the cluster, i.e., what happen
5 matches
Mail list logo