fix(inputs.kafka_consumer): Fix deadlock #16074
Merged
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.
Summary
PR fixes a potential deadlock that most often could occur when
plugin.Stop()
was called immediately afterplugin.Start()
- this situation was most likely to happen during the execution of unit tests.I also removed
ticker
, which was never initialized. It was likely a leftover from some functionality that no longer exists.Root cause:
In the
Stop()
method,k.topicLock.Lock()
was called along withdefer k.topicLock.Unlock()
.This caused
k.topicLock
to remain locked until theStop()
method finished executing.At the very end of the
Stop()
method,k.wg.Wait()
was waiting for all goroutines to complete.Meanwhile, in the
Start()
method, a goroutine was started, which got stuck atk.topicLock.Lock()
because it was waiting fork.topicLock
to be unlocked (which would only happen after theStop()
method finished).Checklist
Related stacktrace: