# Unable to load more than 30000 fields into index pattern **URL:** \ **Category:** Kibana\ **Created:** [April 14, 2021, 8:16am UTC](https://discuss.elastic.co/t/unable-to-load-more-than-30000-fields-into-index-pattern/270088 "2021-04-14T08:16:13Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![TomasK](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tomask/32/87026_2.png) [@TomasK](https://discuss.elastic.co/u/TomasK)\ **Post date:** [April 14, 2021, 8:16am UTC](https://discuss.elastic.co/t/unable-to-load-more-than-30000-fields-into-index-pattern/270088/1 "2021-04-14T08:16:13Z")
Hi everybody! I have index pattern let's say `myindex_*` which includes many other indexes like: ```auto myindex_client1_* myindex_client2_* myindex_client3_* myindex_client4_* etc... ``` the indexes like `myindex_clientN_*` have about 200 to 500 fields. Some are the same for every index some are unique for the specific client. This all add up to more than 32 000 fields in the `myindex_*` index pattern. Right now the `myindex_*` index pattern shows just about 4800 fields. When I try to refresh the index pattern it did looks like it did nothing still showing just about 4800 fields, but when I click on the let's say `Scripted fields` the page got refreshed and the Fields tab suddenly shows more than 32 000 fields. But when I again click to Discover or Dashboards and than go back to the Index Patterns and click on `myindex_*` there is again just about 4800. It never gets saved with the 32000 fields. I was getting 413 response code in the Kibana logs, but I solved it by adding `http.max_content_length: 500mb` to elastic config on every node and restarting the whole cluster. Now there is no errors in the kibana or elastic logs but it still behaves the same. I am using this docker image for Kibana [docker.elastic.co/kibana/kibana-oss:7.9.3](http://docker.elastic.co/kibana/kibana-oss:7.9.3) and the elasticsearch is also 7.9.3 version. Can you please help me to save those fields? Regards Tom ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [April 14, 2021, 8:17am UTC](https://discuss.elastic.co/t/unable-to-load-more-than-30000-fields-into-index-pattern/270088/2 "2021-04-14T08:17:20Z")
Welcome to our community! 😃 I can't help solve your immediate issue sorry. But I would suggest that your field count is excessive and likely to cause you other issues in the future. You should really address that. ---
**Author:** ![wylie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wylie/32/81794_2.png) [@wylie](https://discuss.elastic.co/u/wylie)\ **Post date:** [April 14, 2021, 3:02pm UTC](https://discuss.elastic.co/t/unable-to-load-more-than-30000-fields-into-index-pattern/270088/3 "2021-04-14T15:02:48Z")
I agree- this is an excessive number of fields, and it will slow down Kibana if you try to do this. I'm testing locally with 4000 fields and I keep finding new performance issues. If you really need to show this many fields, I have some suggestions: 1. You could upgrade to 7.11 or 7.12, where we automatically pull the field list from the mappings when needed. This will prevent the issue where you can't save. 2. You are probably running into the kibana `server.maxPayloadBytes` limit: [Configure Kibana | Kibana Guide [7.12] | Elastic](https://www.elastic.co/guide/en/kibana/current/settings.html) ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [May 12, 2021, 3:03pm UTC](https://discuss.elastic.co/t/unable-to-load-more-than-30000-fields-into-index-pattern/270088/4 "2021-05-12T15:03:07Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.