# LogStash Poll messages

**URL:** <https://discuss.elastic.co/t/logstash-poll-messages/253382>\
**Category:** Logstash\
**Created:** [October 27, 2020, 3:23am UTC](https://discuss.elastic.co/t/logstash-poll-messages/253382 "2020-10-27T03:23:10Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![dfoot](https://avatars.discourse-cdn.com/v4/letter/d/ea5d25/32.png) [@dfoot](https://discuss.elastic.co/u/dfoot)\
**Post date:** [October 27, 2020, 3:23am UTC](https://discuss.elastic.co/t/logstash-poll-messages/253382/1 "2020-10-27T03:23:10Z")

</div>

I am getting below logstash log message that stopping data flow for some reason I had to restart logstash and then re-occur. Please advise.

[org.apache.kafka.clients.consumer.internals.AbstractCoordinator] [Consumer clientId=logstash-0, groupId=logstash] This member will leave the group because consumer poll timeout has expired. This means the time between subsequent calls to poll() was longer than the configured max.poll.interval.ms, which typically implies that the poll loop is spending too much time processing messages. You can address this either by increasing max.poll.interval.ms or by reducing the maximum size of batches returned in poll() with max.poll.records.  
[2020-09-28T09:28:48,673][INFO][org.apache.kafka.clients.consumer.internals.AbstractCoordinator] [Consumer clientId=logstash-0, groupId=logstash] Sending LeaveGroup request to coordinator xxx-xxx-xxxx.dco.local:9092 (id: 2147483647 rack: null)

---

<div class="post-metadata">

**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\
**Post date:** [October 27, 2020, 2:38pm UTC](https://discuss.elastic.co/t/logstash-poll-messages/253382/2 "2020-10-27T14:38:20Z")

</div>

Sounds like back pressure from the pipeline is causing the input to suffer a timeout. Without knowing that the pipeline and outputs are doing it is impossible to improve on the advice in the error message.

---

<div class="post-metadata">

**Author:** ![dfoot](https://avatars.discourse-cdn.com/v4/letter/d/ea5d25/32.png) [@dfoot](https://discuss.elastic.co/u/dfoot)\
**Post date:** [October 27, 2020, 3:46pm UTC](https://discuss.elastic.co/t/logstash-poll-messages/253382/3 "2020-10-27T15:46:15Z")

</div>

We use Kafka for queue management, let me know what I need to check and share the details of pipeline and outputs.

---

<div class="post-metadata">

**Author:** ![dfoot](https://avatars.discourse-cdn.com/v4/letter/d/ea5d25/32.png) [@dfoot](https://discuss.elastic.co/u/dfoot)\
**Post date:** [October 29, 2020, 2:09pm UTC](https://discuss.elastic.co/t/logstash-poll-messages/253382/4 "2020-10-29T14:09:22Z")

</div>

Hi,

I suggest to add below on Logstash (7.1.1) input Kafka (2.2.1), not sure if this will resolve the issue with the poll time out and the values may need change as its guessing also I may not need them all. Can you confirm please.

heartbeat\_interval\_ms =\> "1000"  
poll\_timeout\_ms =\> "10000"  
session\_timeout\_ms =\> "120000"  
request\_timeout\_ms =\> "130000"  
consumer\_threads =\> 40

Let me know

Dave

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [November 26, 2020, 2:09pm UTC](https://discuss.elastic.co/t/logstash-poll-messages/253382/5 "2020-11-26T14:09:24Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.