# Allocation via \_id vs \_ip **URL:** \ **Category:** Elasticsearch\ **Created:** [September 11, 2012, 4:43pm UTC](https://discuss.elastic.co/t/allocation-via--id-vs--ip/8993 "2012-09-11T16:43:10Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Shairon\_Toledo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shairon_toledo/32/2490_2.png) [@Shairon\_Toledo](https://discuss.elastic.co/u/Shairon_Toledo)\ **Post date:** [September 11, 2012, 4:43pm UTC](https://discuss.elastic.co/t/allocation-via--id-vs--ip/8993/1 "2012-09-11T16:43:10Z")
Hi guys, For instability reason(I guess in Amazon EC2) we're moving our cluster from a zone to another, we're doing this node by node. Using allocation API by \_ip I can exclude a node from cluster. When I include a new node by \_ip curl -XPUT localhost:9200/\_cluster/settings -d '{ "transient" : { "cluster.routing.allocation.include.\_ip" : "10.34.2.1,10.34.2.2,10.34.2.3,10.34.2.4" } }' I see the new node on \_cluser/\_nodes but shards is not initializing on it even in a period of 3 hours after performed the command, I already tried in transient and persistent mode. However when I include using \_id the shards start initializing right away. How you experienced something like that? If so, how to troubleshoot that? I don't like the idea to use \_id for allocate nodes if a node fail and need be restarted, the id become other. Best, -- Shairon Toledo [http://hashcode.me](http://hashcode.me) -- ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 3:13am UTC](https://discuss.elastic.co/t/allocation-via--id-vs--ip/8993/2 "2017-07-06T03:13:10Z")
Closed on July 6, 2017, 3:13am UTC