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 plugin could cause logstash to crash if sync timeout occurs #293

Open
vbohata opened this issue Nov 1, 2018 · 1 comment
Open
Assignees
Labels

Comments

@vbohata
Copy link
Contributor

vbohata commented Nov 1, 2018

In Logstash 6.4, kafka input plugin 8.2.0 sometimes if sync timeout occurs it just crashes the whole logstash. So the following error follows crash:

Exception in thread "Ruby-0-Thread-28: /opt/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-input-kafka-8.2.0/lib/logstash/inputs/kafka.rb:242" Exception in thread "Ruby-0-Thread-35: /opt/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-input-kafka-8.2.0/lib/logstash/inputs/kafka.rb:242" Exception in thread "Ruby-0-Thread-32: /opt/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-input-kafka-8.2.0/lib/logstash/inputs/kafka.rb:242" org.apache.kafka.common.KafkaException: Unexpected error from SyncGroup: The request timed out.
at org.apache.kafka.clients.consumer.internals.AbstractCoordinator$SyncGroupResponseHandler.handle(org/apache/kafka/clients/consumer/internals/AbstractCoordinator.java:638)
at org.apache.kafka.clients.consumer.internals.AbstractCoordinator$SyncGroupResponseHandler.handle(org/apache/kafka/clients/consumer/internals/AbstractCoordinator.java:611)
at org.apache.kafka.clients.consumer.internals.AbstractCoordinator$CoordinatorResponseHandler.onSuccess(org/apache/kafka/clients/consumer/internals/AbstractCoordinator.java:894)
at org.apache.kafka.clients.consumer.internals.AbstractCoordinator$CoordinatorResponseHandler.onSuccess(org/apache/kafka/clients/consumer/internals/AbstractCoordinator.java:874)
at org.apache.kafka.clients.consumer.internals.RequestFuture$1.onSuccess(org/apache/kafka/clients/consumer/internals/RequestFuture.java:204)
at org.apache.kafka.clients.consumer.internals.RequestFuture.fireSuccess(org/apache/kafka/clients/consumer/internals/RequestFuture.java:167)
at org.apache.kafka.clients.consumer.internals.RequestFuture.complete(org/apache/kafka/clients/consumer/internals/RequestFuture.java:127)
at org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient$RequestFutureCompletionHandler.fireCompletion(org/apache/kafka/clients/consumer/internals/ConsumerNetworkClient.java:586)
at org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.firePendingCompletedRequests(org/apache/kafka/clients/consumer/internals/ConsumerNetworkClient.java:400)

@jsvd jsvd added the bug label Nov 5, 2018
@jsvd jsvd self-assigned this Nov 5, 2018
@colinsurprenant
Copy link
Contributor

probably related to elastic/logstash#11603

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants