Re: mesos leader switch may lead orphan tasks

2016-11-29 Thread Chengwei Yang
On Tue, Nov 29, 2016 at 11:31:58PM +0800, haosdent wrote: > As check with chengwei privately. The orphan tasks should not exist after > framework subscribed success, because could not find them in the > `orphan_tasks` > field in the master/state endpoint. Yeah, thanks @haosdent! > > On Tue, Nov

Re: mesos leader switch may lead orphan tasks

2016-11-29 Thread haosdent
As check with chengwei privately. The orphan tasks should not exist after framework subscribed success, because could not find them in the `orphan_tasks` field in the master/state endpoint. On Tue, Nov 29, 2016 at 9:53 PM, Chengwei Yang wrote: > On Tue, Nov 29, 2016 at 09:31:08PM +0800, haosdent

Re: mesos leader switch may lead orphan tasks

2016-11-29 Thread Chengwei Yang
On Tue, Nov 29, 2016 at 09:31:08PM +0800, haosdent wrote: > Do your jobs scheduled by marathon or your framework? We started 3 frameworks(marathon, storm, chronos) before upgrading. Here is the relative logs from the leading master -8< ...

Re: mesos leader switch may lead orphan tasks

2016-11-29 Thread haosdent
Do your jobs scheduled by marathon or your framework? On Tue, Nov 29, 2016 at 7:20 PM, Chengwei Yang wrote: > Hi there, > > We're upgrading mesos from 0.28.2 to 1.0.2 and we found an interesting > problem. > > We followed the official upgrade guide so first upgrade 2 following > mesos-master, an

mesos leader switch may lead orphan tasks

2016-11-29 Thread Chengwei Yang
Hi there, We're upgrading mesos from 0.28.2 to 1.0.2 and we found an interesting problem. We followed the official upgrade guide so first upgrade 2 following mesos-master, and then the leading master. Once the leading master upgraded, the leader switched to another 1.0.2 mesos-master. Now, stop