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

Reply via email to