# Kibana Gone RED from Elastic over indexing or something?
**URL:** https://discuss.elastic.co/t/kibana-gone-red-from-elastic-over-indexing-or-something/144617
**Category:** Elasticsearch
**Created:** [August 16, 2018, 4:38am UTC](https://discuss.elastic.co/t/kibana-gone-red-from-elastic-over-indexing-or-something/144617 "2018-08-16T04:38:14Z")
**Posts on this page:** 13
**Page:** 1
### Author:  [@Krittapas\_Jewjaitham](https://discuss.elastic.co/u/Krittapas_Jewjaitham)
#### Post date: [August 16, 2018, 4:38am UTC](https://discuss.elastic.co/t/kibana-gone-red-from-elastic-over-indexing-or-something/144617/1 "2018-08-16T04:38:14Z")
First of all, I'm very new with this kibana and Elastic Search. I'm using it to be search optimization for HPE CM as a search module. And there's a problem that kibana gone RED and freezed.
Now the kibana's status is freezed and unable to config or check any other information but this dashboard.
We guess the issue may from creating too many index for testing the program. So how can I attached some log and screen shot for investigation ?
---
### Author:  [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [August 16, 2018, 6:23am UTC](https://discuss.elastic.co/t/kibana-gone-red-from-elastic-over-indexing-or-something/144617/2 "2018-08-16T06:23:08Z")
Sounds like you are having a problem with Elasticsearch. Is there anything in the Elasticsearch logs? Can you get the output from the [cluster health API](https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-health.html)? How much RAM and heap does your Elasticsearch nodes have? How many indices/shards did you try to create?
---
### Author:  [@Krittapas\_Jewjaitham](https://discuss.elastic.co/u/Krittapas_Jewjaitham)
#### Post date: [August 16, 2018, 7:27am UTC](https://discuss.elastic.co/t/kibana-gone-red-from-elastic-over-indexing-or-something/144617/3 "2018-08-16T07:27:14Z")
Ok, About that as I mentioned ,I'm very new to this.
1. I would like to know how can i get out put from Clust ter health API. ( I cant access the server myself because of the customer's security. I have to send the instruction or how to get it to infrastructure team.
2. I thinks, there's no problems with HEAP SIZE , Because ever checked it before.
Thanks
---
### Author:  [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [August 16, 2018, 8:41am UTC](https://discuss.elastic.co/t/kibana-gone-red-from-elastic-over-indexing-or-something/144617/4 "2018-08-16T08:41:06Z")
To get the stats, use the API I provided a link to. If you need to request information, it may be useful to ask for the output of the [cluster stats API](https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-stats.html) as well. You can retrieve this information via Elasticsearch HTTP interface, e.g. using `curl`.
---
### Author:  [@Krittapas\_Jewjaitham](https://discuss.elastic.co/u/Krittapas_Jewjaitham)
#### Post date: [August 16, 2018, 10:37am UTC](https://discuss.elastic.co/t/kibana-gone-red-from-elastic-over-indexing-or-something/144617/5 "2018-08-16T10:37:32Z")
> [@Christian\_Dahlqvist](#):
>
> Elasticsearch HTTP interface
Yeah, I got that you need the cluster stats information. But I still don't know how to apply this "curl -X GET "localhost:9200/\_cluster/stats?human&pretty" for getting the stat info.
Now the infrastructure team send me as attached , it that help ?
---
### Author:  [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [August 16, 2018, 10:48am UTC](https://discuss.elastic.co/t/kibana-gone-red-from-elastic-over-indexing-or-something/144617/6 "2018-08-16T10:48:49Z")
That looks fine. The cluster is yellow as you only have one node and can not allocate replicas.
---
### Author:  [@Krittapas\_Jewjaitham](https://discuss.elastic.co/u/Krittapas_Jewjaitham)
#### Post date: [August 16, 2018, 10:58am UTC](https://discuss.elastic.co/t/kibana-gone-red-from-elastic-over-indexing-or-something/144617/7 "2018-08-16T10:58:10Z")
Do we need further information for investigation ? If don't , what's the root cause and how to fix this ?
sorry for many question ,but i'm too new about this.
Thanks a lot.
---
### Author:  [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [August 16, 2018, 11:37am UTC](https://discuss.elastic.co/t/kibana-gone-red-from-elastic-over-indexing-or-something/144617/8 "2018-08-16T11:37:27Z")
You could look in the Elasticsearch logs and see if there is any clue as to what happened there.
---
### Author:  [@Krittapas\_Jewjaitham](https://discuss.elastic.co/u/Krittapas_Jewjaitham)
#### Post date: [August 16, 2018, 11:51am UTC](https://discuss.elastic.co/t/kibana-gone-red-from-elastic-over-indexing-or-something/144617/9 "2018-08-16T11:51:35Z")
I got some log from infra team as following. And you still need the stat or not ? Please tell me , what else do you need to solve this out.
- The following log from " **delasticsearch.log**"
[2018-08-15T00:14:12,048][INFO][o.e.m.j.JvmGcMonitorService] [BOTDRM2-AP3-D1] [gc][2589407] overhead, spent [272ms] collecting in the last [1s]
[2018-08-15T18:29:37,118][DEBUG][o.e.a.s.TransportSearchAction] [BOTDRM2-AP3-D1] [hpecm\_dttest][0], node[ZatldygGQ8iXzf5LF7ZbDA], [P], s[STARTED], a[id=OVW9U8cTR3KE2shFYgtYkQ]: Failed to execute [SearchRequest{searchType=QUERY\_THEN\_FETCH, indices=[hpecm\_dttest], indicesOptions=IndicesOptions[id=38, ignore\_unavailable=false, allow\_no\_indices=true, expand\_wildcards\_open=true, expand\_wildcards\_closed=false, allow\_alisases\_to\_multiple\_indices=true, forbid\_closed\_indices=true], types=[record], routing='null', preference='null', requestCache=null, scroll=null, maxConcurrentShardRequests=5, batchedReduceSize=512, preFilterShardSize=128, source={
"from" : 9945,
"size" : 255,
"query" : {
"query\_string" : {
"query" : "_ธปท_",
"fields" : [
"Title^1.0"
],
"use\_dis\_max" : true,
"tie\_breaker" : 0.0,
"default\_operator" : "and",
"auto\_generate\_phrase\_queries" : false,
"max\_determinized\_states" : 10000,
"enable\_position\_increments" : true,
"fuzziness" : "AUTO",
"fuzzy\_prefix\_length" : 0,
"fuzzy\_max\_expansions" : 50,
"phrase\_slop" : 0,
"analyze\_wildcard" : true,
"escape" : false,
"split\_on\_whitespace" : true,
"boost" : 1.0
}
},
"stored\_fields" : "\_id",
"sort" : [
{
"uri" : {
"order" : "asc"
}
}
]
}}] lastShard [true]
org.elasticsearch.transport.RemoteTransportException: [BOTDRM2-AP3-D1][172.29.58.98:9300][indices:data/read/search[phase/query]]
Caused by: org.elasticsearch.search.query.QueryPhaseExecutionException: Result window is too large, from + size must be less than or equal to: [10000] but was [10200]. See the scroll api for a more efficient way to request large data sets. This limit can be set by changing the [index.max\_result\_window] index level setting.
at org.elasticsearch.search.DefaultSearchContext.preProcess(DefaultSearchContext.java:203) ~[elasticsearch-5.6.3.jar:5.6.3]
at org.elasticsearch.search.query.QueryPhase.preProcess(QueryPhase.java:95) ~[elasticsearch-5.6.3.jar:5.6.3]
at org.elasticsearch.search.SearchService.createContext(SearchService.java:497) ~[elasticsearch-5.6.3.jar:5.6.3]
at org.elasticsearch.search.SearchService.createAndPutContext(SearchService.java:461) ~[elasticsearch-5.6.3.jar:5.6.3]
at org.elasticsearch.search.SearchService.executeQueryPhase(SearchService.java:257) ~[elasticsearch-5.6.3.jar:5.6.3]
at org.elasticsearch.action.search.SearchTransportService$6.messageReceived(SearchTransportService.java:343) ~[elasticsearch-5.6.3.jar:5.6.3]
at org.elasticsearch.action.search.SearchTransportService$6.messageReceived(SearchTransportService.java:340) ~[elasticsearch-5.6.3.jar:5.6.3]
at org.elasticsearch.transport.RequestHandlerRegistry.processMessageReceived(RequestHandlerRegistry.java:69) ~[elasticsearch-5.6.3.jar:5.6.3]
at org.elasticsearch.transport.TransportService$7.doRun(TransportService.java:644) [elasticsearch-5.6.3.jar:5.6.3]
at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.doRun(ThreadContext.java:638) [elasticsearch-5.6.3.jar:5.6.3]
at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37) [elasticsearch-5.6.3.jar:5.6.3]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0\_162]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0\_162]
at java.lang.Thread.run(Unknown Source) [?:1.8.0\_162]
Please Help
---
### Author:  [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [August 17, 2018, 6:21am UTC](https://discuss.elastic.co/t/kibana-gone-red-from-elastic-over-indexing-or-something/144617/10 "2018-08-17T06:21:33Z")
I do not se anything in there that would necessarily explain why the cluster went red.
---
### Author:  [@Krittapas\_Jewjaitham](https://discuss.elastic.co/u/Krittapas_Jewjaitham)
#### Post date: [August 17, 2018, 6:52am UTC](https://discuss.elastic.co/t/kibana-gone-red-from-elastic-over-indexing-or-something/144617/11 "2018-08-17T06:52:26Z")
Now we already restart whole service and server. And the status still RED.
So what we have to do now and after.
Thanks
---
### Author:  [@Krittapas\_Jewjaitham](https://discuss.elastic.co/u/Krittapas_Jewjaitham)
#### Post date: [August 17, 2018, 7:31am UTC](https://discuss.elastic.co/t/kibana-gone-red-from-elastic-over-indexing-or-something/144617/12 "2018-08-17T07:31:51Z")
More update. Now elastic is available now. ( Yellow ) . From restart the elastic . But Kibana still red.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [September 14, 2018, 7:31am UTC](https://discuss.elastic.co/t/kibana-gone-red-from-elastic-over-indexing-or-something/144617/13 "2018-09-14T07:31:55Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.