# Shard allocation says max retry but fails to allocate on retry\_failed=true

**URL:** https://discuss.elastic.co/t/shard-allocation-says-max-retry-but-fails-to-allocate-on-retry-failed-true/170396
**Category:** Elasticsearch
**Created:** [February 28, 2019, 6:23pm UTC](https://discuss.elastic.co/t/shard-allocation-says-max-retry-but-fails-to-allocate-on-retry-failed-true/170396 "2019-02-28T18:23:41Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![redcho](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/redcho/32/38931_2.png) [@redcho](https://discuss.elastic.co/u/redcho)
#### Post date: [March 4, 2019, 8:13am UTC](https://discuss.elastic.co/t/shard-allocation-says-max-retry-but-fails-to-allocate-on-retry-failed-true/170396/5 "2019-03-04T08:13:13Z")

</div>

> [@DavidTurner](#):
>
> The message was generated before the counter was reset. If you tried again, I think you would have seen a more recent message.

Actually, I tried more than once to run this command and nothing updated at that response and shards are still unassigned.

Also, just in case, I still check breaker stats on nodes and I believe there is enough room. (Elasticsearch was complaining for CircuitBreakingException[parent] and when I check the parent breaker, at least 4GB available.)

---

_[View the full topic](https://discuss.elastic.co/t/shard-allocation-says-max-retry-but-fails-to-allocate-on-retry-failed-true/170396)._