# Index Routing Allocation basics **URL:** \ **Category:** Elasticsearch\ **Created:** [September 24, 2012, 4:21pm UTC](https://discuss.elastic.co/t/index-routing-allocation-basics/9121 "2012-09-24T16:21:43Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Amit](https://avatars.discourse-cdn.com/v4/letter/a/ee7513/32.png) [@Amit](https://discuss.elastic.co/u/Amit)\ **Post date:** [September 24, 2012, 4:21pm UTC](https://discuss.elastic.co/t/index-routing-allocation-basics/9121/1 "2012-09-24T16:21:43Z")
Hello All, I am trying index routing allocation option available with elastic search. I have gone through the docs available on net, this group and looked through the test cases. But could not come to any substantial conclusion. I have been working with Elastic Search but not from a long time. Hence I would be thankful, if below queries are answered; 1- Does the Index routing allocation work only after the Index is created or can I specify a routing allocation policy and than create an index. index.routing.allocation.exclude.tag: node1, index.routing.allocation.include.tag: node2 etc. 2- a- If the routing policy is applied at the index creation level, than shards should not be created at exclude nodes. And rebalancing of shards will happen between the include nodes. If only one include node is mentioned than no rebalancing should happen hence faster index creation. 2- b- If routing happens after the index is created and rebalancing of shards happen. Than what is the usefulness of routing as it defeats its purpose. 3- Is it possible to use Transport Client and bulk index the documents with routing option. If so how? Please suggest. Thanks Amit -- ---
**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:11am UTC](https://discuss.elastic.co/t/index-routing-allocation-basics/9121/2 "2017-07-06T03:11:41Z")