On Mon, 5 Mar 2012 11:26:20 -0500, Mark Miller
wrote:
On Mar 5, 2012, at 10:01 AM, dar...@ontrenet.com wrote:
If one of those 10 indexing nodes goes down or falls out of sync and
comes
back, does ZK block the state of indexing until that single node
catches
back up?
No - if a node falls ou
On Mar 5, 2012, at 10:01 AM, dar...@ontrenet.com wrote:
> If one of those 10 indexing nodes goes down or falls out of sync and comes
> back, does ZK block the state of indexing until that single node catches
> back up?
No - if a node falls out of sync or comes back, the rest of the cluster
cont
A question relating to this.
If you are running a single ZK node, but say 10 other nodes and then
parallel index on each of those nodes, will the ZK be hit by all 10
indexing nodes constantly? i.e. very chatty?
If one of those 10 indexing nodes goes down or falls out of sync and comes
back, does
On Sun, 4 Mar 2012 21:09:30 -0500, Mark Miller
wrote:
On Mar 4, 2012, at 5:43 PM, Markus Jelsma wrote:
everything stalls after it lists all segment files and that a ZK
state change has occured.
Can you get a stack trace here? I'll try to respond to more tomorrow.
What version of trunk are yo
On Mar 4, 2012, at 5:43 PM, Markus Jelsma wrote:
> everything stalls after it lists all segment files and that a ZK state change
> has occured.
Can you get a stack trace here? I'll try to respond to more tomorrow. What
version of trunk are you using? We have been making fixes and improvements
nodes that are unable to resume
operations.Will try again tomorrow and see if cleaning the Solr dataDir
will help.
Thanks
Original Message ----
Subject: Re: [SoldCloud] Slow indexing
Date: Sun, 4 Mar 2012 22:34:20 +0100
From: eks dev
To: solr-user@lucene.apache.org, markus.jel
hmm, loks like you are facing exactly the phenomena I asked about.
See my question here:
http://comments.gmane.org/gmane.comp.jakarta.lucene.solr.user/61326
On Sun, Mar 4, 2012 at 9:24 PM, Markus Jelsma
wrote:
> Hi,
>
> With auto-committing disabled we can now index many millions of documents in
Hi,
With auto-committing disabled we can now index many millions of
documents in our test environment on a 5-node cluster with 5 shards and
a replication factor of 2. The documents are uploaded from map/reduce.
No significant changes were made to solrconfig and there are no update
processors
