Cherry-pick #12063 to 6.7: Fix memory leak in Filebeat pipeline acker #12139
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cherry-pick of PR #12063 to 6.7 branch. Original message:
Before this change acker goroutine was kept forever as processed events
count was not correctly updated.
Filebeat sends an empty event to update file states, this event is not
published, but treated as dropped, without updating counters.
This change makes sures that
a.events
counter is updated for droppedevents too, so the acker gets closed (and freed) after all ACKs happen.
Original work by @jsoriano (#11810), and input from @urso, thank you both!