# Es restore \[parent\] data too large

**URL:** <https://discuss.elastic.co/t/es-restore-parent-data-too-large/329016>\
**Category:** Elasticsearch\
**Tags:** snapshot-and-restore\
**Created:** [March 31, 2023, 7:21am UTC](https://discuss.elastic.co/t/es-restore-parent-data-too-large/329016 "2023-03-31T07:21:38Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![huang1](https://avatars.discourse-cdn.com/v4/letter/h/7cd45c/32.png) [@huang1](https://discuss.elastic.co/u/huang1)\
**Post date:** [March 31, 2023, 7:21am UTC](https://discuss.elastic.co/t/es-restore-parent-data-too-large/329016/1 "2023-03-31T07:21:38Z")

</div>

The total data size of es is less than 1G. Perform a regular restore. After running for a period of time, throw the [parent] data too large. The node executing the restore has a high xmx and a high CPU utilization rate\_ After analyzing nodes/stat/breaker, it was found that only parent estimated\_ size\_ in\_ The usage of bytes exceeds the limit. Other examples such as requests and accounting are very small.

ES 7.10.0

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [March 31, 2023, 8:24am UTC](https://discuss.elastic.co/t/es-restore-parent-data-too-large/329016/2 "2023-03-31T08:24:44Z")

</div>

You are running a very old version, so I would recommend that you upgrade to at least version 7.17 as soon as possible.

What is the full output of the [cluster stats API](https://www.elastic.co/guide/en/elasticsearch/reference/8.6/cluster-stats.html)?

---

<div class="post-metadata">

**Author:** ![huang1](https://avatars.discourse-cdn.com/v4/letter/h/7cd45c/32.png) [@huang1](https://discuss.elastic.co/u/huang1)\
**Post date:** [March 31, 2023, 9:45am UTC](https://discuss.elastic.co/t/es-restore-parent-data-too-large/329016/3 "2023-03-31T09:45:29Z")

</div>

Is this a known problem? It appears that heap memory has not been freed.

MEMORY\_ MX\_ BEAN.getHeapMemoryUsage().getUsed();

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [March 31, 2023, 11:17am UTC](https://discuss.elastic.co/t/es-restore-parent-data-too-large/329016/4 "2023-03-31T11:17:27Z")

</div>

> [@Christian\_Dahlqvist](#):
>
> What is the full output of the [cluster stats API](https://www.elastic.co/guide/en/elasticsearch/reference/8.6/cluster-stats.html)?

Please answer this question.

---

<div class="post-metadata">

**Author:** ![huang1](https://avatars.discourse-cdn.com/v4/letter/h/7cd45c/32.png) [@huang1](https://discuss.elastic.co/u/huang1)\
**Post date:** [March 31, 2023, 12:01pm UTC](https://discuss.elastic.co/t/es-restore-parent-data-too-large/329016/5 "2023-03-31T12:01:44Z")

</div>

![aa](https://us1.discourse-cdn.com/elastic/original/3X/e/e/eeecf9cdbc01f4fcd3217387b71671ff73b58d1a.jpeg)

The picture shows some validation I did in the test environment; parent estimated\_ Size takes up a lot of memory.

Set indices.breaker.total.use\_real\_memory=false, parent estimated\_size only occupies about 200 kb, and is back to normal.

If i set indices.breaker.total.use\_real\_memory=false, is there anything i need to pay attention to?

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [March 31, 2023, 12:05pm UTC](https://discuss.elastic.co/t/es-restore-parent-data-too-large/329016/6 "2023-03-31T12:05:17Z")

</div>

Please do not show pictures of text. Copy the response and paste it here instead.

---

<div class="post-metadata">

**Author:** ![huang1](https://avatars.discourse-cdn.com/v4/letter/h/7cd45c/32.png) [@huang1](https://discuss.elastic.co/u/huang1)\
**Post date:** [March 31, 2023, 12:22pm UTC](https://discuss.elastic.co/t/es-restore-parent-data-too-large/329016/7 "2023-03-31T12:22:59Z")

</div>

```auto
"breaker": {
	"request": {……},
	"fielddata": {……},
	"in_flight_requests": {……},
	"model_inference": {……},
	"accounting": {……},
	"parent": {
		"limit_size_in_bytes": 2040109465,
		"limit_size": "1.8gb",
		"estimated_size_in_bytes": 845819696,
		"estimated_size": "806.6mb",
		"overhead": 1,
		"tripped": 0
	}
}

```

(request、fielddata、in\_flight\_requests、model\_inference、accounting) memory usages very low; but parent memory usage very high，until data too large.

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [March 31, 2023, 12:34pm UTC](https://discuss.elastic.co/t/es-restore-parent-data-too-large/329016/8 "2023-03-31T12:34:37Z")

</div>

There is a lot of useful information within the response that can help point to the issue, so please post the full response. What you posted is not at all what I am looking for.

---

<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:** [April 28, 2023, 12:35pm UTC](https://discuss.elastic.co/t/es-restore-parent-data-too-large/329016/9 "2023-04-28T12:35:20Z")

</div>

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