### Author:  [@Wilks](https://discuss.elastic.co/u/Wilks)
#### Post date: [July 23, 2019, 3:39pm UTC](https://discuss.elastic.co/t/unable-to-start-kibana-and-circuit-breaking-exception/191860/1 "2019-07-23T15:39:43Z")
Hi,
I am unable to start KIbana 7.2. I get the following message in the browser
"{"statusCode":429,"error":"Too Many Requests","message":"[circuit\_breaking\_exception] [parent] Data too large, data for [\] would be [1021976864/974.6mb], which is larger than the limit of [1003493785/957mb], real usage: [1021976864/974.6mb], new bytes reserved: [0/0b], with { bytes\_wanted=1021976864 & bytes\_limit=1003493785 & durability="PERMANENT" }"}"
I have tried killing the PID, stopping and restarting services and even a full system reboot but I cant seem to get it to start up.
Any thoughts?
thanks
---
### Author:  [@Larry\_Gregory](https://discuss.elastic.co/u/Larry_Gregory)
#### Post date: [July 23, 2019, 3:46pm UTC](https://discuss.elastic.co/t/unable-to-start-kibana-and-circuit-breaking-exception/191860/2 "2019-07-23T15:46:11Z")
@Wilks,
This error is coming from Elasticsearch. What is the state of your cluster right now?
Can you hit Elasticsearch directly? What goes `GET _cluster/health` report?
---
### Author:  [@Wilks](https://discuss.elastic.co/u/Wilks)
#### Post date: [July 23, 2019, 4:29pm UTC](https://discuss.elastic.co/t/unable-to-start-kibana-and-circuit-breaking-exception/191860/3 "2019-07-23T16:29:45Z")
HI,
It displayed the following:
{"cluster\_name":"elasticsearch",
"status":"yellow",
"timed\_out":false,
"number\_of\_nodes":1,
"number\_of\_data\_nodes":1,
"active\_primary\_shards":76,
"active\_shards":76,
"relocating\_shards":0,
"initializing\_shards":0,"
unassigned\_shards":71,
"delayed\_unassigned\_shards":0,
"number\_of\_pending\_tasks":0,
"number\_of\_in\_flight\_fetch":0,
"task\_max\_waiting\_in\_queue\_millis":0,
"active\_shards\_percent\_as\_number":51.70068027210885}
---
### Author:  [@Larry\_Gregory](https://discuss.elastic.co/u/Larry_Gregory)
#### Post date: [July 23, 2019, 7:18pm UTC](https://discuss.elastic.co/t/unable-to-start-kibana-and-circuit-breaking-exception/191860/4 "2019-07-23T19:18:30Z")
When you said you did a full system restart, did that include Elasticsearch as well, or just Kibana? Can you try restarting your cluster?
---
### Author:  [@Wilks](https://discuss.elastic.co/u/Wilks)
#### Post date: [July 23, 2019, 8:41pm UTC](https://discuss.elastic.co/t/unable-to-start-kibana-and-circuit-breaking-exception/191860/5 "2019-07-23T20:41:01Z")
Full restart of underlying OS. So a flat out reboot of the Linux system. I will give that a try
---
### Author:  [@Wilks](https://discuss.elastic.co/u/Wilks)
#### Post date: [July 23, 2019, 9:49pm UTC](https://discuss.elastic.co/t/unable-to-start-kibana-and-circuit-breaking-exception/191860/6 "2019-07-23T21:49:44Z")
Restarted but still no go......the KIbana service never starts up, I mean it starts up for a second and then immediately shuts down..
---
### Author:  [@Larry\_Gregory](https://discuss.elastic.co/u/Larry_Gregory)
#### Post date: [July 24, 2019, 11:35am UTC](https://discuss.elastic.co/t/unable-to-start-kibana-and-circuit-breaking-exception/191860/7 "2019-07-24T11:35:22Z")
I see a similar error here: [Get [parent] Data too large from kibana logs](https://discuss.elastic.co/t/get-parent-data-too-large-from-kibana-logs/190647/10)
Based on that post, do you know which garbage collector you're using with Elasticsearch? Changing to CMS instead of G1GC might help
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [August 21, 2019, 11:35am UTC](https://discuss.elastic.co/t/unable-to-start-kibana-and-circuit-breaking-exception/191860/8 "2019-08-21T11:35:26Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.