Skip to content

Conversation

meelapshah
Copy link
Contributor

I found this bug when I noticed to following:

  1. reboot a mesos slave with slave ID X
  2. the slave comes back up with slave ID Y
  3. chronos successfully runs jobs on the slave
  4. after --agent_reregister_timeout (default 10 mins) passes, mesos master sends SLAVE_LOST for slave ID X
  5. chronos starts launching jobs that are already running

vixns added a commit to vixns/chronos that referenced this pull request Apr 30, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant