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

kafka input problematic consumer threads handling #15

Open
colinsurprenant opened this issue Feb 21, 2020 · 1 comment
Open

kafka input problematic consumer threads handling #15

colinsurprenant opened this issue Feb 21, 2020 · 1 comment
Assignees
Labels
bug Something isn't working int-shortlist

Comments

@colinsurprenant
Copy link
Contributor

the input plugin simply spans a number of consumer threads and join them in the run method:

@runner_threads = @runner_consumers.map { |consumer| thread_runner(logstash_queue, consumer) }
@runner_threads.each { |t| t.join }

This leads to 2 potentially serious problems:

@RogierSchuring
Copy link

Had this exact issue last week.
I expected only the pipeline with the Kafka cluster that was faulty to restart or fail, but was unpleasantly surprised that the whole Logstash agent restarts.

In our case it was expired certificates on some Kafka nodes of one Kafka cluster that caused handshake failures.

Would love a fix for this to prevent this in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working int-shortlist
Projects
None yet
Development

No branches or pull requests

4 participants