How do you ingest it exactly with Atomtic updates ? Is there an update 
processor in-between? 

What are your settings for hard/soft commit?

For the shared going to recovery - do you have a log entry or something ?

What is the Solr version?

How do you setup ZK?

> Am 10.08.2020 um 16:24 schrieb Anshuman Singh <singhanshuma...@gmail.com>:
> 
> Hi,
> 
> We have a SolrCloud cluster with 10 nodes. We have 6B records ingested in
> the Collection. Our use case requires atomic updates ("inc") on 5 fields.
> Now almost 90% documents are atomic updates and as soon as we start our
> ingestion pipelines, multiple shards start going into recovery, sometimes
> all replicas of some shards go into down state.
> The ingestion rate is also too slow with atomic updates, 4-5k per second.
> We were able to ingest records without atomic updates at the rate of 50k
> records per second without any issues.
> 
> What I'm suspecting is, the fact that these "inc" atomic updates
> require fetching of fields before indexing can cause slow rates but what
> I'm not getting is, why are the replicas going into recovery?
> 
> Regards,
> Anshuman

Reply via email to