Cherry-pick #18630 to 7.x: Validate config before init NewInput to avoid uneccessory cleanup and kubernetes watcher leak #18810
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 #18630 to 7.x branch. Original message:
An alternative Fix #18629
When Filebeat using
add_kubernetes_metadata
processor and enabledinput.reload
, It will cause Kubernetes watcher goroutine leaks when the input config is wrong.I looked through the code in
filebeat/input/log/input.go
, notice that there is a defer function to cleanup when executingNewInput
failed.beats/filebeat/input/log/input.go
Line 76 in d11d609
But it seems not easy to add Kubernetes watcher stopping function here, So I move the validate section to the top, then
NewInput
will return directly if the config not qualified.