RE: Solr cloud error during document ingestion

toCommit has >> anything to do with the problem, but I could be wrong about that. Yes, agree. This is not related to autoCommit. -Original Message- From: Shawn Heisey [mailto:apa...@elyograg.org] Sent: Sunday, July 12, 2015 6:25 PM To: solr-user@lucene.apache.org Subject: Re: Solr cl

Re: Solr cloud error during document ingestion

On 7/11/2015 9:33 PM, Tarala, Magesh wrote: > I'm using 4.10.2 in a 3 node solr cloud setup > I have a collection with 3 shards and 2 replicas each. > I'm ingesting solr documents via solrj. > > While ingesting the documents, I get the following error: > > 264147944 [updateExecutor-1-thread-268]

RE: Solr cloud error during document ingestion

creating nested documents. -Original Message- From: Erick Erickson [mailto:erickerick...@gmail.com] Sent: Sunday, July 12, 2015 1:41 PM To: solr-user@lucene.apache.org Subject: Re: Solr cloud error during document ingestion How are you ingesting documents? ExtractingRequestHandler? Tha

Re: Solr cloud error during document ingestion

> want to go near real time. Thanks for the link to your post. It is very > helpful. > > > > -Original Message- > From: Erick Erickson [mailto:erickerick...@gmail.com] > Sent: Sunday, July 12, 2015 11:24 AM > To: solr-user@lucene.apache.org > Subject: Re: Solr clo

RE: Solr cloud error during document ingestion

time. Thanks for the link to your post. It is very helpful. -Original Message- From: Erick Erickson [mailto:erickerick...@gmail.com] Sent: Sunday, July 12, 2015 11:24 AM To: solr-user@lucene.apache.org Subject: Re: Solr cloud error during document ingestion Probably not related to

Re: Solr cloud error during document ingestion

Probably not related to your problem, but if you're sending lots of docs at Solr, committing every 100 is very aggressive. I'm assuming you're committing from the client, which, while OK doesn't scale very well if you ever decide to have more than 1 client sending docs. I'd recommend setting your

Re: Solr cloud error during document ingestion

I suggest to check http://10.222.238.35:8983/solr/serviceorder_shard1_replica2 logs to find root