# Regarding to logstash performance limit

**URL:** <https://discuss.elastic.co/t/regarding-to-logstash-performance-limit/197763>\
**Category:** Logstash\
**Created:** [September 3, 2019, 6:36am UTC](https://discuss.elastic.co/t/regarding-to-logstash-performance-limit/197763 "2019-09-03T06:36:33Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![terrymu](https://avatars.discourse-cdn.com/v4/letter/t/ea666f/32.png) [@terrymu](https://discuss.elastic.co/u/terrymu)\
**Post date:** [September 3, 2019, 6:36am UTC](https://discuss.elastic.co/t/regarding-to-logstash-performance-limit/197763/1 "2019-09-03T06:36:33Z")

</div>

Hi experts,

I have met a logstash performance limit issue, when I parse my log, logstash report this error log:

`

> [2019-09-03T14:21:49,106][WARN][logstash.outputs.elasticsearch] Could not index event to Elasticsearch. {:status=\>400, :action=\>["index", {:\_id=\>nil, :\_index=\>"logstash-2019.09.03", :\_type=\>"\_doc", :\_routing=\>nil}, #LogStash::Event:0x1b6c342a], :response=\>{"index"=\>{"\_index"=\>"logstash-2019.09.03", "\_type"=\>"\_doc", "\_id"=\>"4\_PJ9WwB6iwMcN-ZT20T", "status"=\>400, "error"=\>{"type"=\>"illegal\_argument\_exception", "reason"=\>"Limit of total fields [1000] in index [logstash-2019.09.03] has been exceeded"}}}}

`

That block the parsed data that can't be sent to elasticsearch. From the content, it seems a total fields limit, how can I enlarge this parameter？Or are there some method can solve this issue? Thank you.

---

<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:** [September 3, 2019, 6:56am UTC](https://discuss.elastic.co/t/regarding-to-logstash-performance-limit/197763/2 "2019-09-03T06:56:57Z")

</div>

That is an Elasticsearch limit and not managed through Logstash. How come you have so many fields?

---

<div class="post-metadata">

**Author:** ![terrymu](https://avatars.discourse-cdn.com/v4/letter/t/ea666f/32.png) [@terrymu](https://discuss.elastic.co/u/terrymu)\
**Post date:** [September 3, 2019, 7:12am UTC](https://discuss.elastic.co/t/regarding-to-logstash-performance-limit/197763/3 "2019-09-03T07:12:51Z")

</div>

The log is included a lot of data that I have added a lot of index to map them, therefore the index count is huge, are there some method can enlarge the mapping.total\_fields.limit ?

I have retrieved the similar issue, here is a method to enlarge it, i will try to do it later.

```
curl -XPUT localhost:9200/_template/twothousandfieldslimit -d '
{
    "order" : 1,
    "template" : "twitter*",
    "settings" : {
        "index" : {
            "mapping.total_fields.limit" : "2000"
         }
    }
}'
```

---

<div class="post-metadata">

**Author:** ![terrymu](https://avatars.discourse-cdn.com/v4/letter/t/ea666f/32.png) [@terrymu](https://discuss.elastic.co/u/terrymu)\
**Post date:** [September 10, 2019, 8:30am UTC](https://discuss.elastic.co/t/regarding-to-logstash-performance-limit/197763/4 "2019-09-10T08:30:41Z")

</div>

The solution is:

> curl -XPUT [http://localhost:9200/lsh\_nokia\_nokiasbc-2019.09.\*/\_settings/?pretty](http://localhost:9200/lsh_nokia_nokiasbc-2019.09.*/_settings/?pretty) -H 'Content-Type: application/json' -d ' { "index.mapping.total\_fields.limit" : "2000" } '

---

<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:** [October 8, 2019, 8:30am UTC](https://discuss.elastic.co/t/regarding-to-logstash-performance-limit/197763/5 "2019-10-08T08:30:45Z")

</div>

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