# What might cause an updated index to fail relocating shards?

**URL:** https://discuss.elastic.co/t/what-might-cause-an-updated-index-to-fail-relocating-shards/65661
**Category:** Elasticsearch
**Created:** [November 10, 2016, 12:53pm UTC](https://discuss.elastic.co/t/what-might-cause-an-updated-index-to-fail-relocating-shards/65661 "2016-11-10T12:53:49Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![julrich](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/julrich/32/13094_2.png) [@julrich](https://discuss.elastic.co/u/julrich)
#### Post date: [November 10, 2016, 12:53pm UTC](https://discuss.elastic.co/t/what-might-cause-an-updated-index-to-fail-relocating-shards/65661/1 "2016-11-10T12:53:49Z")

</div>

Hey everyone!

I've encountered a problem, where setting new allocation settings on an index doesn't seem to trigger reallocation of shards. I'm trying to implement rollover-logic, and I'm failing on this step, which is necessary before shrinking the index.

I'm following this blogpost here:

> **[And the big one said "Rollover" — Managing Elasticsearch time-based indices...](https://www.elastic.co/blog/managing-time-based-indices-efficiently)**
>
> Introducing the new Rollover Pattern, and the APIs which support it, which is a simpler, more efficient way of managing time-based indices in Elasticsearch.

I've reduced my problem to a simple test case, and included the resulting log output here:

> <https://gist.github.com/julrich/7dcc96797e3931ceca55e639fa3229ae>

Maybe someone spots an error? Or are there settings on the cluster level I should look out for?

Thanks in advance!  
Jonas

---

<div class="post-metadata">

### Author: ![julrich](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/julrich/32/13094_2.png) [@julrich](https://discuss.elastic.co/u/julrich)
#### Post date: [November 10, 2016, 1:34pm UTC](https://discuss.elastic.co/t/what-might-cause-an-updated-index-to-fail-relocating-shards/65661/2 "2016-11-10T13:34:39Z")

</div>

Actually found the problem. The code is perfectly fine, it was just my nodes were not registering with their correct hostname as name. This is why the allocation couldn't be executed, as there was no such node as specified.

---

<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: [December 8, 2016, 1:34pm UTC](https://discuss.elastic.co/t/what-might-cause-an-updated-index-to-fail-relocating-shards/65661/3 "2016-12-08T13:34:58Z")

</div>

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