It’s still registered after a few hours… I don’t see a shutdown in the list of endpoints for /master. What version was that introduced?
Here’s the list I see: /master/health<http://usrs1021.pit.twosigma.com:5050/help/master/health> /master/observe<http://usrs1021.pit.twosigma.com:5050/help/master/observe> /master/redirect<http://usrs1021.pit.twosigma.com:5050/help/master/redirect> /master/roles.json<http://usrs1021.pit.twosigma.com:5050/help/master/roles.json> /master/state.json<http://usrs1021.pit.twosigma.com:5050/help/master/state.json> /master/stats.json<http://usrs1021.pit.twosigma.com:5050/help/master/stats.json> /master/tasks.json<http://usrs1021.pit.twosigma.com:5050/help/master/tasks.json> From: [email protected] [mailto:[email protected]] On Behalf Of Vinod Kone Sent: Tuesday, August 05, 2014 1:54 PM To: [email protected] Subject: Re: stale framework registrations On Tue, Aug 5, 2014 at 9:48 AM, David Palaitis <[email protected]<mailto:[email protected]>> wrote: I recently stopped Marathon but it is still registered with the Mesos Masters. I started a new instance of Marathon and it has re-registered successfully with a new framework Id. I’d like to understand how to force deregistration of the stale framework. Master should remove the old framework after its failover timeout has elapsed. If you want to force it, there is also a "/master/shutdown" (see: <masterip>:5050/help/master/shutdown) endpoint on the master.
