Well, you have to monitor. That's the down-side to using this type of routing, you're effectively saying "I know enough about my usage to predict".
What do you think you're gaining by using this? Putting all docs from a single org on a subset of your servers reduces some part of the parallelism you get from sharding. So unless you have a very specific use case and some data to back it up I wonder why you even want to try to control it like this ;) Best, Erick On Thu, Nov 2, 2017 at 7:51 AM, Ketan Thanki <ktha...@asite.com> wrote: > Hi, > > I have 4 shard and 4 replica and I do Composite document routing for my > unique field 'Id' as mentions below. > e.g : tenants bits use as projectId/2! prefix with Id > > how to ensure that one shard does not get overloaded when we use routing > > Regards, > Ketan. > Please cast a vote for Asite in the 2017 Construction Computing Awards: Click > here to Vote<http://caddealer.com/concompawards/index.php?page=cca2017vote> > > [CC Award Winners!] >
