Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix multi-master event handling bug #19790

Merged
merged 2 commits into from Jan 17, 2015
Merged

Conversation

cachedout
Copy link
Contributor

We had a situation wherein minion generators would race to the sub
socket and only a single minion would actually act on the package. The
result was that events such as refresh_pillar would cause one (or
sometimes both) minions to stop responding. This changes the behaviour
so that the first instance to get the request calls action on all
instances.

While this has the possible side-effect of blocking for O(n) inside the event
handling loop, it also ensures that multi-master minions update in a
linear fashion.

Mike Place added 2 commits January 16, 2015 10:33
We had a situation wherein minion generators would race to the sub
socket and only a single minion would actually act on the package. The
result was that events such as refresh_pillar would cause one (or
sometimes both) minions to stop responding. This changes the behaviour
so that the first instance to get the request calls action on all
instances.

While this has the possible side-effect of blocking for O(n) inside the event
handling loop, it also ensures that multi-master minions update in a
linear fashion.
@thatch45
Copy link
Member

Go Go Jenkins!

thatch45 added a commit that referenced this pull request Jan 17, 2015
Fix multi-master event handling bug
@thatch45 thatch45 merged commit 5c2ce4c into saltstack:develop Jan 17, 2015
@rallytime
Copy link
Contributor

@cachedout is this something that should be backported to 2014.7?

@rallytime rallytime added the bugfix-bckport will be be back-ported to an older release branch by creating a PR against that branch label Jan 22, 2015
@rallytime rallytime added ZZZ[Done]-back-ported-bf RETIRED The pull request has been back-ported to an older branch. and removed bugfix-bckport will be be back-ported to an older release branch by creating a PR against that branch labels Jan 22, 2015
thatch45 added a commit that referenced this pull request Jan 22, 2015
rallytime pushed a commit that referenced this pull request Jan 23, 2015
thatch45 added a commit that referenced this pull request Jan 23, 2015
@rallytime
Copy link
Contributor

It appears that when the previous attempt at a backport was reverted, I never backported this change to 2015.2. The above PR remedies that.

jfindlay added a commit that referenced this pull request Feb 24, 2015
cro pushed a commit to cro/salt that referenced this pull request Feb 28, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ZZZ[Done]-back-ported-bf RETIRED The pull request has been back-ported to an older branch.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants