Update are batched, but it's on a per-request basis. So, if you're sending one document at a time you'll won't get any batching. If you send 10 docs at a time and they happen to go to 10 different shards, you'll get 10 different update requests.
If you're sending 1,000 docs per update you' should be seeing some batching going on. bq: but why not batch them up or give a option to batch N updates in either of the above case I suspect what you're seeing is that you're not sending very many docs per update request and so are being mislead. But that's a guess since you haven't provided much in the way of data on _how_ you're updating. bq: the cloud eventually starts to fail How? Details matter. Best Erick On Wed, Jun 19, 2013 at 4:23 AM, Asif <talla...@gmail.com> wrote: > Hi, > > I had questions on implementation of Sharding and Replication features of > Solr/Cloud. > > 1. I noticed that when sharding is enabled for a collection - individual > requests are sent to each node serving as a shard. > > 2. Replication too follows above strategy of sending individual documents > to the nodes serving as a replica. > > I am working with a system that requires massive number of writes - I have > noticed that due to above reason - the cloud eventually starts to fail > (Even though I am using a ensemble). > > I do understand the reason behind individual updates - but why not batch > them up or give a option to batch N updates in either of the above case - I > did come across a presentation that talked about batching 10 updates for > replication at least, but I do not think this is the case. > - Asif
