lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Markus Jelsma <markus.jel...@openindex.io>
Subject RE: SolrCloud indexing blocks if node is recovering
Date Sat, 03 Nov 2012 09:23:17 GMT
Hi - yes, i should be able to make sense out of them next monday. I assume you're not too interested
in the OOM machine but all surrounding nodes that blocked instead? 
 


-----Original message-----
> From:Mark Miller <markrmiller@gmail.com>
> Sent: Sat 03-Nov-2012 03:14
> To: solr-user@lucene.apache.org
> Subject: Re: SolrCloud indexing blocks if node is recovering
> 
> Doesn't sound right. Still have the logs?
> 
> - Mark
> 
> On Fri, Nov 2, 2012 at 9:45 AM, Markus Jelsma
> <markus.jelsma@openindex.io> wrote:
> > Hi,
> >
> > We just tested indexing some million docs from Hadoop to a 10 node 2 rep SolrCloud
cluster with this week's trunk. One of the nodes gave an OOM but indexing continued without
interruption. When i restarted the node indexing stopped completely, the node tried to recover
- which was unsuccessful. I restarted the node again but that wasn't very helpful either.
Finally i decided to stop the node completely and see what happens - indexing resumed.
> >
> > Why or how won't the other nodes accept incoming documents when one node behaves
really bad? The dying node wasn't the node we were sending documents to and we are not using
CloudSolrServer yet (see other thread). Is this known behavior? Is it a bug?
> >
> > Thanks,
> > Markus
> 
> 
> 
> -- 
> - Mark
> 

Mime
View raw message