mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Raul Gutierrez Segales (JIRA)" <>
Subject [jira] [Commented] (MESOS-2681) Slave process must restart to update ensemble members
Date Thu, 30 Apr 2015 19:52:06 GMT


Raul Gutierrez Segales commented on MESOS-2681:

well, hold on - nowadays bouncing a slave is cheap right? so this shouldn't be a huge deal,

> Slave process must restart to update ensemble members
> -----------------------------------------------------
>                 Key: MESOS-2681
>                 URL:
>             Project: Mesos
>          Issue Type: Bug
>          Components: slave
>            Reporter: Joe Smith
> Right now, if a ZooKeeper ensemble has (for instance) more observers added to it, the
Mesos Slaves will not see them, and continue to attempt to connect to only the original members.
A restart of the slave process is required to call {{getaddrinfo}} again and enumerate the
list of hosts in the ensemble.
> Subsequent {{getaddrinfo}} calls _will only_ occur when {{zookeeper_init()}} is called
again, that is to say: when the old session expires and you need to create a new one. If you
swap all hosts in your ensemble too fast, without permitting time for old sessions to expire,
you'd end up with clients looping forever, trying to connect to the old servers in order to
get its old session expired.
> This is best tracked by ZOOKEEPER-1998, where these is some discussion about a necessary
improvement to the implementation already in the 3.5.x branch, or putting this functionality
(debatably a feature vs. fixing a bug) in 3.4.x.
> (Thanks to [~rgs] for reviewing this as well)

This message was sent by Atlassian JIRA

View raw message