Skip to content
This repository has been archived by the owner on Jan 30, 2020. It is now read-only.

No job offers were sent due to rolling update #131

Closed
robszumski opened this issue Feb 18, 2014 · 3 comments
Closed

No job offers were sent due to rolling update #131

robszumski opened this issue Feb 18, 2014 · 3 comments

Comments

@robszumski
Copy link
Member

After a rolling update, job offers were not sent out when one of the machines went down. list-units still showed an old machine running the units. The etcd cluster was not affected by this update other than a leader election.

Starting and stopping the units fixed the problem.

@robszumski robszumski added the bug label Feb 18, 2014
@bcwaldon
Copy link
Contributor

When the one machine rebooted, it should have caused a MachineRemoved event to go out to the rest of the cluster. One of those other machines should have responded accordingly by cleaning up that now-removed machine's artifacts from the cluster (including the defunct job states).

I'm not sure why this didn't happen, but it could have been due to a race with the leader election.

Still something to look into.

@bcwaldon
Copy link
Contributor

This might actually be due to the same root cause of #149

@bcwaldon bcwaldon added this to the v0.1.4 milestone Feb 22, 2014
@bcwaldon
Copy link
Contributor

Closing as dupe of #149 as fix is in hand. Please reopen if the problem persists.

@bcwaldon bcwaldon removed this from the v0.1.4 milestone Feb 24, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants