# Disclaimer on "Customizing Your Document Routing" article?

**URL:** <https://discuss.elastic.co/t/disclaimer-on-customizing-your-document-routing-article/32919>\
**Category:** Elasticsearch\
**Created:** [October 24, 2015, 6:07pm UTC](https://discuss.elastic.co/t/disclaimer-on-customizing-your-document-routing-article/32919 "2015-10-24T18:07:00Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Joshua\_Haas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joshua_haas/32/5461_2.png) [@Joshua\_Haas](https://discuss.elastic.co/u/Joshua_Haas)\
**Post date:** [October 24, 2015, 6:07pm UTC](https://discuss.elastic.co/t/disclaimer-on-customizing-your-document-routing-article/32919/1 "2015-10-24T18:07:00Z")

</div>

Does anyone know what the big disclaimer at the top of [https://www.elastic.co/blog/customizing-your-document-routing](https://www.elastic.co/blog/customizing-your-document-routing) means?

I'm trying to transition from a one-index-per-user setup (which was killing me because of RAM usage) to a many-users-per-index setup. So routing is something I want to make sure I understand ... this article is very helpful, except it's explicitly warning not to trust it!!

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [October 24, 2015, 6:33pm UTC](https://discuss.elastic.co/t/disclaimer-on-customizing-your-document-routing-article/32919/2 "2015-10-24T18:33:41Z")

</div>

I think that one of the reason is that you can not extract routing key from the doc anymore IIRC from 2.0.

Apart from that, I still think routing is good. 🙂

---

<div class="post-metadata">

**Author:** ![Ravi\_Shanker\_Reddy](https://avatars.discourse-cdn.com/v4/letter/r/a5b964/32.png) [@Ravi\_Shanker\_Reddy](https://discuss.elastic.co/u/Ravi_Shanker_Reddy)\
**Post date:** [July 6, 2016, 2:43pm UTC](https://discuss.elastic.co/t/disclaimer-on-customizing-your-document-routing-article/32919/3 "2016-07-06T14:43:41Z")

</div>

I studied the routing concept in the above mentioned link. But my need is totally different. I have three type of logs like Prepaid, Postpaid & CDMA. The traffic is little bit high (1200 per second from each). I mostly search based on the type. For that I neeeded routing. But I cant allocate only one shard per type as like in the manual. So I want to allocate 5 shards for postpaid and route all the postpaid traffic to the 5 shards and so on for others also. The routing is based on the path  
`/home/ES/POSTPAID/SMSCDR_POSTPAID_160518010000_10.80.41.70_RS1.log /home/ES/CDMA/SMSCDR_DEL_ATTEMPT_160518000000_10.80.41.68_RS3_1.log /home/ES/PREPAID/SMSCDR_PREPAID_160518220000_10.80.41.88_RS10.log`

Allocate 5 shards for one type.  
Note: I cant maintain three indices for these three. I have indices based on the operator.

Hope I am understandable..

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [July 6, 2016, 3:29pm UTC](https://discuss.elastic.co/t/disclaimer-on-customizing-your-document-routing-article/32919/4 "2016-07-06T15:29:24Z")

</div>

I don't believe you have another choice than building one index per type `prepaid`, `postpaid`and `cdma`.  
On the opposite you can totally send all documents for the same operator within the same shard using routing.

---

<div class="post-metadata">

**Author:** ![Ravi\_Shanker\_Reddy](https://avatars.discourse-cdn.com/v4/letter/r/a5b964/32.png) [@Ravi\_Shanker\_Reddy](https://discuss.elastic.co/u/Ravi_Shanker_Reddy)\
**Post date:** [July 6, 2016, 3:40pm UTC](https://discuss.elastic.co/t/disclaimer-on-customizing-your-document-routing-article/32919/5 "2016-07-06T15:40:53Z")

</div>

These are same in the performance???

`1 index with 30 shards 3 indexes with 10 shards each`

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [July 6, 2016, 5:09pm UTC](https://discuss.elastic.co/t/disclaimer-on-customizing-your-document-routing-article/32919/6 "2016-07-06T17:09:18Z")

</div>

Searching in 30 shards, wherever they are in 30 indices / 1 shard or 1 index / 30 shards has the same cost.

But remember that you want to use routing here.

So basically you will search in 3 shards at most.

---

<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:** [July 5, 2017, 10:37pm UTC](https://discuss.elastic.co/t/disclaimer-on-customizing-your-document-routing-article/32919/7 "2017-07-05T22:37:37Z")

</div>


