# Index pattern - circuit break and cannot read property of null

**URL:** <https://discuss.elastic.co/t/index-pattern-circuit-break-and-cannot-read-property-of-null/189285>\
**Category:** Kibana\
**Created:** [July 8, 2019, 5:42am UTC](https://discuss.elastic.co/t/index-pattern-circuit-break-and-cannot-read-property-of-null/189285 "2019-07-08T05:42:06Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Simran\_Chauhan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/simran_chauhan/32/49586_2.png) [@Simran\_Chauhan](https://discuss.elastic.co/u/Simran_Chauhan)\
**Post date:** [July 8, 2019, 5:42am UTC](https://discuss.elastic.co/t/index-pattern-circuit-break-and-cannot-read-property-of-null/189285/1 "2019-07-08T05:42:06Z")

</div>

Hello , I have documented API's which include which tags they belong to, their request and response parameters, description, hostname.  
each API goes up to 2000+ lines and up to date, I have pushed approximately 200 such files in .json format.

All the files have been indexed on the localhost.  
the OS I'm using is Windows 10 and the Kibana version is 7.1.0.

I have indexed the APIs on the basis of tags. If an API is to be used for finance, it's indexed under api\_finance index, similarly, if some API is used for transport its indexed in api\_transport.

However, when I try to create an index pattern api\*, Kibana seems to be loading for error and display

1. Circuit breaking error which disconnects the kibana server on the command prompt window. It reconnects and disconnects and keeps on repeating the same error.
2. cannot read property 'message' of null on the kibana browser window

I have tried using aliases by assigning "demo" as an alias for all the indices and then tried  
creating the index pattern.  
index pattern creates when I trying it with 10 files only but the error appears when I try with the whole documentation of 200 files.

Can someone please help me out?

 ![null%20error](https://us1.discourse-cdn.com/elastic/original/3X/1/d/1d558cdf7fa358aee730d68f8e0da009805af33a.png)

---

<div class="post-metadata">

**Author:** ![joshdover](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joshdover/32/42020_2.png) [@joshdover](https://discuss.elastic.co/u/joshdover)\
**Post date:** [July 8, 2019, 3:58pm UTC](https://discuss.elastic.co/t/index-pattern-circuit-break-and-cannot-read-property-of-null/189285/2 "2019-07-08T15:58:06Z")

</div>

Do these indices have the same mapping fields? If not, it's possible the index pattern being created is exceeding practical [limits for the number of fields](https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping.html#mapping-limit-settings).

What do your mappings look like? If you're using any array fields, Elasticsearch may be handling these in ways that you may not expect that leads to a large number of unique mapping fields. Any more context here on the mappings would help me give more concrete advice 🙂

---

<div class="post-metadata">

**Author:** ![Simran\_Chauhan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/simran_chauhan/32/49586_2.png) [@Simran\_Chauhan](https://discuss.elastic.co/u/Simran_Chauhan)\
**Post date:** [July 9, 2019, 4:05am UTC](https://discuss.elastic.co/t/index-pattern-circuit-break-and-cannot-read-property-of-null/189285/3 "2019-07-09T04:05:55Z")

</div>

The mappings for each index differs slightly.  
I earlier got an error for limit for number of lines which I resolved by increasing the limit for the index.

**PUT index\_name/\_settings**  
**{**  
**"index.mapping.total\_field.limit":100000;**  
**}**

I will attach images of the mapping for 2 different indices.

cloud index mapping

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/d/4/d4d68ae4c0778bd4d341ad06fb0567c96467e7db.png)

article index

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/3/5/359227136fafc1291c3d95b160fdf3db8330c4e2.png)

Thank you

---

<div class="post-metadata">

**Author:** ![joshdover](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joshdover/32/42020_2.png) [@joshdover](https://discuss.elastic.co/u/joshdover)\
**Post date:** [July 9, 2019, 4:04pm UTC](https://discuss.elastic.co/t/index-pattern-circuit-break-and-cannot-read-property-of-null/189285/4 "2019-07-09T16:04:21Z")

</div>

Ok let's dig into the weeds a bit.

Can you post the response details for the request to `/api/index_patterns/_fields_for_wildcard` from the Developer Tools "Network" tab in your web browser?

This should help us figure out why the response isn't what is expected.

---

<div class="post-metadata">

**Author:** ![Simran\_Chauhan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/simran_chauhan/32/49586_2.png) [@Simran\_Chauhan](https://discuss.elastic.co/u/Simran_Chauhan)\
**Post date:** [July 10, 2019, 4:51am UTC](https://discuss.elastic.co/t/index-pattern-circuit-break-and-cannot-read-property-of-null/189285/5 "2019-07-10T04:51:54Z")

</div>

the output shows that the mapping is larger than 10Mb

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/e/4/e432f2d927c6e7b3809d1ff76ff6358cd89a7c12.png)

---

<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 7, 2019, 4:51am UTC](https://discuss.elastic.co/t/index-pattern-circuit-break-and-cannot-read-property-of-null/189285/6 "2019-08-07T04:51:54Z")

</div>

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