# Indicie refreshing problem

**URL:** <https://discuss.elastic.co/t/indicie-refreshing-problem/89177>\
**Category:** Kibana\
**Created:** [June 13, 2017, 11:32am UTC](https://discuss.elastic.co/t/indicie-refreshing-problem/89177 "2017-06-13T11:32:13Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![magerRV](https://avatars.discourse-cdn.com/v4/letter/m/8c91f0/32.png) [@magerRV](https://discuss.elastic.co/u/magerRV)\
**Post date:** [June 13, 2017, 11:32am UTC](https://discuss.elastic.co/t/indicie-refreshing-problem/89177/1 "2017-06-13T11:32:13Z")

</div>

We got an Index with around 8K fields and everytime I refresh Kibana it resets the Indicie fields to 5.  
Is there a maximum of fields that Kibana can hold or handle with ? Or is this just an storage problem ?

Im working on Kibana 5.0 . Are there bugfixes for this issue in later versions?

---

<div class="post-metadata">

**Author:** ![Brandon\_Kobel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/brandon_kobel/32/14829_2.png) [@Brandon\_Kobel](https://discuss.elastic.co/u/Brandon_Kobel)\
**Post date:** [June 13, 2017, 1:39pm UTC](https://discuss.elastic.co/t/indicie-refreshing-problem/89177/2 "2017-06-13T13:39:50Z")

</div>

@magerRV are you only seeing 5 fields when refreshing the fields?

Are you using Chrome to refresh the fields list? There's an undocumented maximum XMLHttpRequest response size that you might be hitting in Chrome, that I've seen cause this behavior before. Do you happen to have access to a modern build of Safari, and could you try refreshing the fields list using Safari?

---

<div class="post-metadata">

**Author:** ![magerRV](https://avatars.discourse-cdn.com/v4/letter/m/8c91f0/32.png) [@magerRV](https://discuss.elastic.co/u/magerRV)\
**Post date:** [June 13, 2017, 1:46pm UTC](https://discuss.elastic.co/t/indicie-refreshing-problem/89177/3 "2017-06-13T13:46:38Z")

</div>

@Brandon_Kobel first I see 5 fields after re-indexing I get around around 8K fields. But after creating e.g. a scripted field and refreshing Kibana it goes back to 5 fields.

we have 5 indicies (4 of them between 1500 und 2500 fields) but the largest with around 8K doesnt seem to be safed after refreshing Kibana. I think it could come with an cashing or space Problem ?!

I'm using Firefox for Kibana. Do you think its a browser based problem ?

---

<div class="post-metadata">

**Author:** ![magerRV](https://avatars.discourse-cdn.com/v4/letter/m/8c91f0/32.png) [@magerRV](https://discuss.elastic.co/u/magerRV)\
**Post date:** [June 13, 2017, 1:48pm UTC](https://discuss.elastic.co/t/indicie-refreshing-problem/89177/4 "2017-06-13T13:48:54Z")

</div>

Actually it doesnt matter if I creat anything. After refresh my Kibana tab it goes back to 5 fields all the time. (Only in this case, the other 4 indicies dont have any problem)

---

<div class="post-metadata">

**Author:** ![Brandon\_Kobel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/brandon_kobel/32/14829_2.png) [@Brandon\_Kobel](https://discuss.elastic.co/u/Brandon_Kobel)\
**Post date:** [June 13, 2017, 1:51pm UTC](https://discuss.elastic.co/t/indicie-refreshing-problem/89177/5 "2017-06-13T13:51:01Z")

</div>

@magerRV when hitting the maximum response for a XMLHttpRequest in Firefox, I've generally seen an error logged in the browser console. Would you mind checking Firefox's console to see if any error is logged when refreshing the fields? To open the Firefox console, if you right-click on the page and then select "Inspect Element" , and then open the "Console" tab highlighted below:

 ![](https://us1.discourse-cdn.com/elastic/original/3X/b/7/b707f29550ddf5d5c68be14f48d5c6e6b78078c0.png)

---

<div class="post-metadata">

**Author:** ![magerRV](https://avatars.discourse-cdn.com/v4/letter/m/8c91f0/32.png) [@magerRV](https://discuss.elastic.co/u/magerRV)\
**Post date:** [June 13, 2017, 1:59pm UTC](https://discuss.elastic.co/t/indicie-refreshing-problem/89177/6 "2017-06-13T13:59:53Z")

</div>

Error: Request to Elasticsearch failed: "Bad Request"  
KbnError@[http://rqv04346:5601/bundles/commons.bundle.js?v=14438:63:26369](http://rqv04346:5601/bundles/commons.bundle.js?v=14438:63:26369)  
errors.RequestFailure@[http://rqv04346:5601/bundles/commons.bundle.js?v=14438:63:27570](http://rqv04346:5601/bundles/commons.bundle.js?v=14438:63:27570)  
exports.default/\</\<@[http://rqv04346:5601/bundles/kibana.bundle.js?v=14438:26:14954](http://rqv04346:5601/bundles/kibana.bundle.js?v=14438:26:14954)  
processQueue@[http://rqv04346:5601/bundles/commons.bundle.js?v=14438:38:23621](http://rqv04346:5601/bundles/commons.bundle.js?v=14438:38:23621)  
scheduleProcessQueue/\<@[http://rqv04346:5601/bundles/commons.bundle.js?v=14438:38:23888](http://rqv04346:5601/bundles/commons.bundle.js?v=14438:38:23888)  
$RootScopeProvider/this.$get\</Scope.prototype.$eval@[http://rqv04346:5601/bundles/commons.bundle.js?v=14438:39:4607](http://rqv04346:5601/bundles/commons.bundle.js?v=14438:39:4607)  
$RootScopeProvider/this.$get\</Scope.prototype.$digest@[http://rqv04346:5601/bundles/commons.bundle.js?v=14438:39:2343](http://rqv04346:5601/bundles/commons.bundle.js?v=14438:39:2343)  
$RootScopeProvider/this.$get\</Scope.prototype.$apply@[http://rqv04346:5601/bundles/commons.bundle.js?v=14438:39:5026](http://rqv04346:5601/bundles/commons.bundle.js?v=14438:39:5026)  
done@[http://rqv04346:5601/bundles/commons.bundle.js?v=14438:37:25016](http://rqv04346:5601/bundles/commons.bundle.js?v=14438:37:25016)  
completeRequest@[http://rqv04346:5601/bundles/commons.bundle.js?v=14438:37:28702](http://rqv04346:5601/bundles/commons.bundle.js?v=14438:37:28702)  
createHttpBackend/\</xhr.onload@[http://rqv04346:5601/bundles/commons.bundle.js?v=14438:37:29634](http://rqv04346:5601/bundles/commons.bundle.js?v=14438:37:29634)

thats what I get by re-indexing

mutating the [[Prototype]] of an object will cause your code to run very slowly; instead create the object with the correct initial [[Prototype]] value using Object.create commons.bundle.js:45:21299  
window.controllers sollte nicht mehr verwendet werden. Verwenden Sie es nicht für die Browser-Erkennung.  
("window.controllers souldnt be used. Dont use it for browser detection")  
kibana.bundle.js:93:1248  
setting active api to [es\_5\_0] kibana.bundle.js:114:17926  
loading default index pattern commons.bundle.js:55  
Index Patterns: index pattern set to .kibana commons.bundle.js:2:5796  
complete in 523.64ms

thats what I get after refreshing Kibana

---

<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:** [July 11, 2017, 2:00pm UTC](https://discuss.elastic.co/t/indicie-refreshing-problem/89177/7 "2017-07-11T14:00:01Z")

</div>

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