# Curator action : allocation dies with exception error

**URL:** <https://discuss.elastic.co/t/curator-action-allocation-dies-with-exception-error/72741>\
**Category:** Elasticsearch\
**Created:** [January 25, 2017, 8:55am UTC](https://discuss.elastic.co/t/curator-action-allocation-dies-with-exception-error/72741 "2017-01-25T08:55:22Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![YuWatanabe](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yuwatanabe/32/13259_2.png) [@YuWatanabe](https://discuss.elastic.co/u/YuWatanabe)\
**Post date:** [January 25, 2017, 8:55am UTC](https://discuss.elastic.co/t/curator-action-allocation-dies-with-exception-error/72741/1 "2017-01-25T08:55:22Z")

</div>

Curator version : elasticsearch-curator (4.2.5)  
Elasticsearch version :elasticsearch-5.1.1

I was testing the curator setting using the configuration from [this blog](https://www.elastic.co/blog/hot-warm-architecture-in-elasticsearch-5-x). However, allocation action dies with exception error.

`2017-01-25 17:36:25,427 ERROR curator.cli cli:193 Failed to complete action: allocation. <class 'curator.exceptions.FailedExecution'>: Exception encountered. Rerun with loglevel DEBUG and/or check Elasticsearch logs for more information. Exception: TransportError(400, u'illegal_argument_exception', u'wait_for_relocating_shards has been removed, use wait_for_no_relocating_shards [true/false] instead')`

As the error shows , [code](https://github.com/elastic/curator/blob/8fd6863d8b401c39524fb3dcc8c1fdb49ffa85b1/curator/actions.py) uses **wait\_for\_relocating\_shards**.  
According to the [release note](https://www.elastic.co/guide/en/elasticsearch/reference/5.1/breaking_50_rest_api_changes.html#_literal_wait_for_relocating_shards_literal_is_now_literal_wait_for_no_relocating_shards_literal_in_literal__cluster_health_literal) option name had changed in 5.1.

Would this be a bug?

---

<div class="post-metadata">

**Author:** ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)\
**Post date:** [January 25, 2017, 9:31pm UTC](https://discuss.elastic.co/t/curator-action-allocation-dies-with-exception-error/72741/2 "2017-01-25T21:31:46Z")

</div>

More like a regression caused by API changes. This is the struggle of trying to maintain code compatibility between major versions of a product.

Please report this in an issue at [https://github.com/elastic/curator](https://github.com/elastic/curator)

---

<div class="post-metadata">

**Author:** ![YuWatanabe](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yuwatanabe/32/13259_2.png) [@YuWatanabe](https://discuss.elastic.co/u/YuWatanabe)\
**Post date:** [January 26, 2017, 2:24am UTC](https://discuss.elastic.co/t/curator-action-allocation-dies-with-exception-error/72741/3 "2017-01-26T02:24:08Z")

</div>

Ok . Thanks.

Posting done.

> <https://github.com/elastic/curator/issues/871>

---

<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:** [February 23, 2017, 2:24am UTC](https://discuss.elastic.co/t/curator-action-allocation-dies-with-exception-error/72741/4 "2017-02-23T02:24:19Z")

</div>

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