# Logstash failed to process cluster event (put-mapping) within 30s

**URL:** <https://discuss.elastic.co/t/logstash-failed-to-process-cluster-event-put-mapping-within-30s/186129>\
**Category:** Logstash\
**Created:** [June 17, 2019, 6:04pm UTC](https://discuss.elastic.co/t/logstash-failed-to-process-cluster-event-put-mapping-within-30s/186129 "2019-06-17T18:04:25Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rajeev\_Prakash](https://avatars.discourse-cdn.com/v4/letter/r/a9a28c/32.png) [@Rajeev\_Prakash](https://discuss.elastic.co/u/Rajeev_Prakash)\
**Post date:** [June 17, 2019, 6:04pm UTC](https://discuss.elastic.co/t/logstash-failed-to-process-cluster-event-put-mapping-within-30s/186129/1 "2019-06-17T18:04:25Z")

</div>

logstash failed to process cluster event (put-mapping) within 30s

Thanks for the help in advance

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [June 17, 2019, 6:23pm UTC](https://discuss.elastic.co/t/logstash-failed-to-process-cluster-event-put-mapping-within-30s/186129/2 "2019-06-17T18:23:02Z")

</div>

This typically means that you cluster is overloaded or have a very large cluster state. A common cause for slowness is large number of indices and shards. How many do you have in your cluster?

---

<div class="post-metadata">

**Author:** ![Rajeev\_Prakash](https://avatars.discourse-cdn.com/v4/letter/r/a9a28c/32.png) [@Rajeev\_Prakash](https://discuss.elastic.co/u/Rajeev_Prakash)\
**Post date:** [June 18, 2019, 1:49pm UTC](https://discuss.elastic.co/t/logstash-failed-to-process-cluster-event-put-mapping-within-30s/186129/3 "2019-06-18T13:49:57Z")

</div>

we were generating the indices on daily basis,and shards we were having more than 4000

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [June 18, 2019, 4:19pm UTC](https://discuss.elastic.co/t/logstash-failed-to-process-cluster-event-put-mapping-within-30s/186129/4 "2019-06-18T16:19:02Z")

</div>

That is a lot of shards, especially if you have a small cluster and/or an old version. What is the specification of your cluster?

---

<div class="post-metadata">

**Author:** ![Rajeev\_Prakash](https://avatars.discourse-cdn.com/v4/letter/r/a9a28c/32.png) [@Rajeev\_Prakash](https://discuss.elastic.co/u/Rajeev_Prakash)\
**Post date:** [June 21, 2019, 1:58pm UTC](https://discuss.elastic.co/t/logstash-failed-to-process-cluster-event-put-mapping-within-30s/186129/5 "2019-06-21T13:58:04Z")

</div>

Issue resolved we re-configured the logstash configuration file again.

Thanks @Christian_Dahlqvist

---

<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:** [July 19, 2019, 1:58pm UTC](https://discuss.elastic.co/t/logstash-failed-to-process-cluster-event-put-mapping-within-30s/186129/6 "2019-07-19T13:58:08Z")

</div>

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