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

Cherry-pick #12458 to 7.2: [Heartbeat] Fix Continuation Dispatch / mode: all pings #12477

Merged
merged 1 commit into from
Jun 7, 2019

Conversation

andrewvc
Copy link
Contributor

@andrewvc andrewvc commented Jun 7, 2019

Cherry-pick of PR #12458 to 7.2 branch. Original message:

Currently mode: all pings are broken. The root cause is that the scheduler dispatch of continuations in the heartbeat task model is broken. Since the only current use of this is mode:all pings that is what is affected. The issue was incorrectly aliasing variables when dispatching future work.

This patch also renames some of the related variables to make understanding the code here simpler.

This issue is well described on this wiki page https://github.com/golang/go/wiki/CommonMistakes

Currently mode: all pings are broken. The root cause is that the scheduler dispatch of continuations in the heartbeat task model is broken. Since the only current use of this is `mode:all` pings that is what is affected. The issue was incorrectly aliasing variables when dispatching future work.

This issue is well described on this wiki page https://github.com/golang/go/wiki/CommonMistakes

(cherry picked from commit e491e9a)
@andrewvc andrewvc requested a review from a team as a code owner June 7, 2019 13:50
@andrewvc andrewvc merged commit 7b285eb into elastic:7.2 Jun 7, 2019
@andrewvc andrewvc deleted the backport_12458_7.2 branch June 7, 2019 14:51
leweafan pushed a commit to leweafan/beats that referenced this pull request Apr 28, 2023
… (elastic#12477)

Currently mode: all pings are broken. The root cause is that the scheduler dispatch of continuations in the heartbeat task model is broken. Since the only current use of this is `mode:all` pings that is what is affected. The issue was incorrectly aliasing variables when dispatching future work.

This issue is well described on this wiki page https://github.com/golang/go/wiki/CommonMistakes

(cherry picked from commit 4cc0a1c)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants