Agent reregistration timeout, no TASK_LOST messages

Hi all, We're using Mesos 1.1.0 and have observed some unexpected behavior with regards to Agent reregistration on our cluster. When a health check failure happens, our framework (in this case Apache Aurora) receives an Agent Lost message along with TASK_LOST messages for each of the tasks that

[GitHub] mesos issue #205: Clarify existence of FrameworkID in SUBSCRIBE calls.

Github user aaronjwood commented on the issue: https://github.com/apache/mesos/pull/205 @neilconway you had mentioned a while back that this could be clarified better. Can you elaborate on what you were thinking so we can get this merged in? --- If your project is set up for it,

Re: Mesos 1.1.3 release

Folks, We are planning to cut the 1.1.3 release once MESOS-7643 is resolved. If you have any patch that needs to get into 1.1.3, please make sure that either it is already in the 1.1.x branch or the corresponding ticket has a target version including 1.1.3. The release dashboard: