# Timeout Error in logstash

**URL:** <https://discuss.elastic.co/t/timeout-error-in-logstash/92656>\
**Category:** Logstash\
**Created:** [July 11, 2017, 1:21pm UTC](https://discuss.elastic.co/t/timeout-error-in-logstash/92656 "2017-07-11T13:21:43Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![swatititame](https://avatars.discourse-cdn.com/v4/letter/s/d6d6ee/32.png) [@swatititame](https://discuss.elastic.co/u/swatititame)\
**Post date:** [July 11, 2017, 1:21pm UTC](https://discuss.elastic.co/t/timeout-error-in-logstash/92656/1 "2017-07-11T13:21:43Z")

</div>

", "\_id"=\>"AV0xCZcO0YIn9Z-Da2uz", "status"=\>400, "error"=\>{"type"=\>"illegal\_argu  
ment\_exception", "reason"=\>"Document contains at least one immense term in field  
="prd\_ErrorMessage" (whose UTF8 encoding is longer than the max length 32766),  
all of which were skipped. Please correct the analyzer to not produce such ter  
ms. The prefix of the first immense term is: '[10, 83, 121, 115, 116, 101, 109,  
32, 101, 120, 99, 101, 112, 116, 105, 111, 110, 32, 10, 91, 69, 88, 67, 69, 80,  
84, 73, 79, 78, 93]...', original message: bytes can be at most 32766 in length  
; got 51151", "caused\_by"=\>{"type"=\>"max\_bytes\_length\_exceeded\_exception", "reas  
on"=\>"bytes can be at most 32766 in length; got 51151"}}}}}  
[2017-07-11T04:45:01,994][ERROR][logstash.instrument.periodicpoller.jvm] Periodi  
cPoller: exception {:poller=\>#\<LogStash::Instrument::PeriodicPoller::JVM:0x5284c  
1c5 @task=#\<Concurrent  
, :excep  
tion=\>#\<Concurrent::TimeoutError: Concurrent::TimeoutError\>, :executed\_at=\>2017-  
07-11 04:45:01 -0500}  
[2017-07-11T04:45:02,887][ERROR][logstash.filters.grok] Error while attempti  
ng to check/cancel excessively long grok patterns {:message=\>"Mutex relocking by  
same thread", :

[2017-07-11T04:45:02,906][WARN][logstash.filters.grok] Timeout executing gr  
ok '(

1.I am loading data from log files in that prd\_ErrorMessage field is loading data which is longer than the max length.

2.I applied "ignore\_above": 256 which resolves my timeout error but I don't want to loose data.  
ignore\_above": 256 will ignore the whole record.

3.I can see my CPU % is also reaches to 100%.  
4.And while loading dashboard ion kibana I am facing below error.  
RemoteTransportException[[Corona][143.22.209.122:9300][indices:data/read/search[  
phase/query]]]; nested: CircuitBreakingException[[request] Data too large, data  
for [\<reused\_arrays\>] would be larger than limit of [381891379/364.1mb]];  
Caused by: CircuitBreakingException[[request] Data too large, data for [\<reused\_  
arrays\>] would be larger than limit of [381891379/364.1mb]]

Please suggest some solution for this issue.

---

<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:** [August 8, 2017, 1:22pm UTC](https://discuss.elastic.co/t/timeout-error-in-logstash/92656/2 "2017-08-08T13:22:20Z")

</div>

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