# Limit exceeded message needs some analysis

**URL:** <https://discuss.elastic.co/t/limit-exceeded-message-needs-some-analysis/94798>\
**Category:** Elasticsearch\
**Created:** [July 27, 2017, 1:01pm UTC](https://discuss.elastic.co/t/limit-exceeded-message-needs-some-analysis/94798 "2017-07-27T13:01:29Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![sentinel](https://avatars.discourse-cdn.com/v4/letter/s/fbc32d/32.png) [@sentinel](https://discuss.elastic.co/u/sentinel)\
**Post date:** [July 27, 2017, 1:01pm UTC](https://discuss.elastic.co/t/limit-exceeded-message-needs-some-analysis/94798/1 "2017-07-27T13:01:29Z")

</div>

Hello

I am getting a lot of these debug messages in Elastic 5.4 setup. Surely this is not up to a 1000. Is there anything I can do to limit this?

curl -s -XGET [http://1localhost:8089/logstash-2017.07.24/\_mapping?pretty](http://1localhost:8089/logstash-2017.07.24/_mapping?pretty) | grep type | wc -l  
**307**  
I don't get this 😞

[2017-07-27T09:46:02,606][DEBUG][o.e.a.b.TransportShardBulkAction] [tZ-k4Bz] [logstash-2017.07.27][2] failed to execute bulk item (index) BulkShardRequest [[logstash-2017.07.27][2]] containing [index {[logstash-2017.07.27][pfactory-log][AV2DcFG-WcoJ2PrqU8ow], source[{"@timestamp":"2017-07-27T09:46:01.929Z","message":"2017-07-27T09:46:01,335 [INFO][Client-Push:2:2][PriceRequestListener] Received PriceRequest: std\_hdr { msg\_type: "PriceRequest" sender\_comp\_id: "akka\_external-2" target\_comp\_id: "PF" sending\_time: 1501148761335 reply\_to: "IR9CJb6mJkxRP5bGXqIUynq2v0o" } subscription\_id: "6db7e5e9-6bc4-11e7-8f77-d89d672383e8" lease\_period: 120000 product: FX\_SPOT ccy\_pair: "CHFMXN" base\_ccy\_dealt: true dealt\_ccy\_amt: "0" client\_side: TWO\_WAY source: "SX" dealing\_method: ESP end\_user\_id: "user\_stg" end\_user\_role: "SYSTEM" in\_competition: UNKNOWN on\_behalf: false from TumTransportContext{realm='nsp://localhost:9003', subject='pf-uat-ln4'} message id 3946151","@version":"1","path":"/data01/orion2/logs/pf-uat-ln4.log","host":"[localhost.net](http://localhost.net)","type":"pfactory-log","elastic\_source\_type":"pfactory-log","logpath":"/data01/orion2/logs/pf-uat-ln4.log","timestamp":"2017-07-27T09:46:01","tz":"335","loglevel":"INFO","Thread":"Client-Push:2:2","EventType":"PriceRequestListener","realm":"nsp://localhost:9003","PriceRequest":"std\_hdr","msg\_type":"PriceRequest","sender\_comp\_id":"akka\_external-2","target\_comp\_id":"PF","sending\_time":"1501148761335","reply\_to":"IR9CJb6mJkxRP5bGXqIUynq2v0o","subscription\_id":"6db7e5-6bc4-11e7-77-d89d672383e8","lease\_period":"120000","product":"FX\_SPOT","ccy\_pair":"CHFMXN","base\_ccy\_dealt":"true","dealt\_ccy\_amt":"0","client\_side":"TWO\_WAY","source":"SX","dealing\_method":"ESP","end\_user\_id":"user\_stg","end\_user\_role":"SYSTEM","in\_competition":"UNKNOWN","on\_behalf":"false","subject":"pf-uat-ln4"}]}]  
**java.lang.IllegalArgumentException: Limit of total fields [1000] in index [logstash-2017.07.27] has been exceeded**  
\*\* at org.elasticsearch.index.mapper.MapperService.checkTotalFieldsLimit(MapperService.java:593)\*\* ~[elasticsearch-5.4.2.jar:5.4.2]

---

<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:** [July 27, 2017, 1:08pm UTC](https://discuss.elastic.co/t/limit-exceeded-message-needs-some-analysis/94798/2 "2017-07-27T13:08:48Z")

</div>

What do you get if you look at the mappings for the index Elasticsearch is complaining about (`logstash-2017.07.27`)?

---

<div class="post-metadata">

**Author:** ![sentinel](https://avatars.discourse-cdn.com/v4/letter/s/fbc32d/32.png) [@sentinel](https://discuss.elastic.co/u/sentinel)\
**Post date:** [July 27, 2017, 2:25pm UTC](https://discuss.elastic.co/t/limit-exceeded-message-needs-some-analysis/94798/3 "2017-07-27T14:25:07Z")

</div>

Sorry

The list is too long and I don't have access to pastebin. It's 4901 lines

---

<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:** [July 27, 2017, 2:30pm UTC](https://discuss.elastic.co/t/limit-exceeded-message-needs-some-analysis/94798/4 "2017-07-27T14:30:02Z")

</div>

What do you get if you run your grep on it?

---

<div class="post-metadata">

**Author:** ![sentinel](https://avatars.discourse-cdn.com/v4/letter/s/fbc32d/32.png) [@sentinel](https://discuss.elastic.co/u/sentinel)\
**Post date:** [July 27, 2017, 2:33pm UTC](https://discuss.elastic.co/t/limit-exceeded-message-needs-some-analysis/94798/5 "2017-07-27T14:33:21Z")

</div>

[user@localhost logs]$ curl -s -XGET [http://localhost:9200/logstash-2017.07.27/\_mapping?pretty](http://localhost:9200/logstash-2017.07.27/_mapping?pretty) | grep type | wc -l  
863

---

<div class="post-metadata">

**Author:** ![sentinel](https://avatars.discourse-cdn.com/v4/letter/s/fbc32d/32.png) [@sentinel](https://discuss.elastic.co/u/sentinel)\
**Post date:** [July 27, 2017, 2:41pm UTC](https://discuss.elastic.co/t/limit-exceeded-message-needs-some-analysis/94798/6 "2017-07-27T14:41:33Z")

</div>

Still not a thousand. What do you make of it?

---

<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:** [July 27, 2017, 2:56pm UTC](https://discuss.elastic.co/t/limit-exceeded-message-needs-some-analysis/94798/7 "2017-07-27T14:56:27Z")

</div>

Do you have something that generates lots of dynamic field names? Do you use a lot of different types that you generate on the fly?

---

<div class="post-metadata">

**Author:** ![sentinel](https://avatars.discourse-cdn.com/v4/letter/s/fbc32d/32.png) [@sentinel](https://discuss.elastic.co/u/sentinel)\
**Post date:** [July 27, 2017, 3:01pm UTC](https://discuss.elastic.co/t/limit-exceeded-message-needs-some-analysis/94798/8 "2017-07-27T15:01:21Z")

</div>

Ok, I'm running a kv filter through the unstructured data and generating some fields. They are limited but I suppose I may have to tone it down some more.

---

<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 24, 2017, 3:01pm UTC](https://discuss.elastic.co/t/limit-exceeded-message-needs-some-analysis/94798/9 "2017-08-24T15:01:30Z")

</div>

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