lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Emir Arnautović <>
Subject Re: how to ensure that one shard does not get overloaded when we use routing
Date Fri, 03 Nov 2017 09:30:01 GMT
Hi Ketan,
I’ll just add that with 4 shards you might just as well skip bits part - all tenant document
will end up on a single shard anyway.
Unless you have a lot projectIds or all have pretty much the same number of documents, and
you always search single projectId, I would reevaluate using routing since it can give you
more troubles then benefits. 

Monitoring - Log Management - Alerting - Anomaly Detection
Solr & Elasticsearch Consulting Support Training -

> On 2 Nov 2017, at 16:15, Erick Erickson <> wrote:
> 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 <> 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<>
>> [CC Award Winners!]

View raw message