# UNASSIGNED ALLOCATION\_FAILED

**URL:** <https://discuss.elastic.co/t/unassigned-allocation-failed/323128>\
**Category:** Elasticsearch\
**Created:** [January 13, 2023, 12:08pm UTC](https://discuss.elastic.co/t/unassigned-allocation-failed/323128 "2023-01-13T12:08:43Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Ayush\_Mathur](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ayush_mathur/32/77134_2.png) [@Ayush\_Mathur](https://discuss.elastic.co/u/Ayush_Mathur)\
**Post date:** [January 13, 2023, 12:28pm UTC](https://discuss.elastic.co/t/unassigned-allocation-failed/323128/2 "2023-01-13T12:28:27Z")

</div>

What is the ES version being used? It seems the data is too large to be handled by heap memory available to the Elasticsearch node.  
I believe something similar was discussed for 7.x version, you can refer to: [Elasticsearch 7.x circuit breaker - data too large - troubleshoot - Stack Overflow](https://stackoverflow.com/questions/60075253/elasticsearch-7-x-circuit-breaker-data-too-large-troubleshoot)

Also, from this disucssion forum earlier posts: [CircuitBreakingException - Data too large - Meta Elastic / Elastic Tips and Common Fixes - Discuss the Elastic Stack](https://discuss.elastic.co/t/circuitbreakingexception-data-too-large/243633)

---

_[View the full topic](https://discuss.elastic.co/t/unassigned-allocation-failed/323128)._