solrcloud - forward update to a shard failed

[Aileen <ai...@kriel.org>]

Keep getting "forward update to shard ....  failed" error.  Not sure if someone else had seen it and is able to resolve.  

Here is our set-up: running solrcloud 4.3.1 on 4 hosts -  2 shards, 2 replications.   Updates are from two different SolrCloud Server connections, with hard commits every 1000 documents.   We are using composite id document routing to control which shard the documents could go.

Thanks in advance for your help.

Re: solrcloud - forward update to a shard failed

["michael.boom" <my...@yahoo.com>]

Do you do your commit from the two indexing clients or have the autocommit
set to maxDocs = 1000 ?



-----
Thanks,
Michael
--
View this message in context: http://lucene.472066.n3.nabble.com/solrcloud-forward-update-to-a-shard-failed-tp4100608p4100633.html
Sent from the Solr - User mailing list archive at Nabble.com.

Re: solrcloud - forward update to a shard failed

[Erick Erickson <er...@gmail.com>]

Here's a writeup on the interactions between a number of the parameters
for soft/hard commits, NRT, and transaction logs. FWIW.

http://searchhub.org/2013/08/23/understanding-transaction-logs-softcommit-and-commit-in-sorlcloud/

Best,
Erick


On Thu, Nov 14, 2013 at 8:22 AM, Aileen <ai...@kriel.org> wrote:

> Thanks Michael.  Followed your advice - no commits from indexing clients;
> let auto commit takes care of things.  It worked, so far no errors.   The
> config params needs some more tweaking to get the right balance,
> specifically maxTime, maxDocs and the soft commit interval, but otherwise
> sold is a lot more healthier...
>
> Thanks for your help.
>
>
> >
> >
> > I did something like that also, and i was getting some nasty problems
> when one of my clients would try to commit before a commit issued by
> another one hadn't yet finish. Might be the same problem for you too.
> >
> > Try not doing explicit commits fomr the indexing client and instead set
> the autocommit to 1000 docs or whichever value fits you best.
> >
> >
> >
> >
> > -----
> > Thanks,
> > Michael
> > --
> > View this message in context:
> http://lucene.472066.n3.nabble.com/solrcloud-forward-update-to-a-shard-failed-tp4100608p4100670.html
> > Sent from the Solr - User mailing list archive at Nabble.com.
>
>

Re: solrcloud - forward update to a shard failed

[Aileen <ai...@kriel.org>]

Thanks Michael.  Followed your advice - no commits from indexing clients; let auto commit takes care of things.  It worked, so far no errors.   The config params needs some more tweaking to get the right balance, specifically maxTime, maxDocs and the soft commit interval, but otherwise sold is a lot more healthier...

Thanks for your help.


> 
> 
> I did something like that also, and i was getting some nasty problems when one of my clients would try to commit before a commit issued by another one hadn't yet finish. Might be the same problem for you too.
> 
> Try not doing explicit commits fomr the indexing client and instead set the autocommit to 1000 docs or whichever value fits you best.
> 
> 
> 
> 
> -----
> Thanks,
> Michael
> --
> View this message in context: http://lucene.472066.n3.nabble.com/solrcloud-forward-update-to-a-shard-failed-tp4100608p4100670.html
> Sent from the Solr - User mailing list archive at Nabble.com.

Re: solrcloud - forward update to a shard failed

["michael.boom" <my...@yahoo.com>]

I did something like that also, and i was getting some nasty problems when
one of my clients would try to commit before a commit issued by another one
hadn't yet finish. Might be the same problem for you too.

Try not doing explicit commits fomr the indexing client and instead set the
autocommit to 1000 docs or whichever value fits you best.




-----
Thanks,
Michael
--
View this message in context: http://lucene.472066.n3.nabble.com/solrcloud-forward-update-to-a-shard-failed-tp4100608p4100670.html
Sent from the Solr - User mailing list archive at Nabble.com.