You can use CloudSolrServer (if you're using Java) which will route documents correctly to the leader of the appropriate shard.
On Tue, Jul 15, 2014 at 3:04 PM, ian <ian.willi...@wales.nhs.uk> wrote: > Hi Mark > > Thanks for replying to my post. Would you know whether my findings are > consistent with what other people see when using SolrCloud? > > One thing I want to investigate is whether I can route my updates to the > correct shard in the first place, by having my client using the same > hashing > logic as Solr, and working out in advance which shard my inserts should be > sent to. Do you know whether that's an approach that others have used? > > Thanks again > Ian > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Slow-inserts-when-using-Solr-Cloud-tp4146087p4147183.html > Sent from the Solr - User mailing list archive at Nabble.com. > -- Regards, Shalin Shekhar Mangar.
