Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: pass (athena.apache.org: message received from 54.191.145.13
 which is an MX secondary for solr-user@lucene.apache.org)
MIME-Version: 1.0
In-Reply-To: 
 <CAJ0odX5xocBPPsmvP0oBzggoEK9e403BnGvQTY0OrM785Q8U8Q@mail.gmail.com>
References: 
 <CAJqdU2-TTL+Qv_f2MLOpcgP-jqMOE5rq491KOfECGh7zm_6XAw@mail.gmail.com>
	<553E5E10.60009@elyograg.org>
	<CAJ0odX5xocBPPsmvP0oBzggoEK9e403BnGvQTY0OrM785Q8U8Q@mail.gmail.com>
Date: Tue, 28 Apr 2015 14:38:31 +0530
Message-ID: 
 <CAJqdU29vDdmS5t8fJeMK5=qBSZ2cRYU9oXKezrKNNuWWPQp4hw@mail.gmail.com>
Subject: Re: Solr node going to recovering state during heavy reindexing
From: Gopal Jee <gopal.jee@myntra.com>
To: solr-user@lucene.apache.org
Content-Type: multipart/alternative; boundary=001a11400532d671d60514c534e1

--001a11400532d671d60514c534e1
Content-Type: text/plain; charset=UTF-8

Thanks Shawn for the insight. WIll try your recommendations .

Gopal

On Mon, Apr 27, 2015 at 9:46 PM, Rajesh Hazari <rajeshhazari@gmail.com>
wrote:

> thanks, i am sure that we have missed this command line property, this
> gives me more information on how to use latest solr scripts more
> effectively.
>
>
> *Thanks,*
> *Rajesh**.*
>
> On Mon, Apr 27, 2015 at 12:04 PM, Shawn Heisey <apache@elyograg.org>
> wrote:
>
> > On 4/27/2015 9:15 AM, Gopal Jee wrote:
> > > We have a 26 node solr cloud cluster. During heavy re-indexing, some of
> > > nodes go into recovering state.
> > > as per current config, soft commit is set to 15 minute and hard commit
> to
> > > 30 sec. Moreover, zkClientTimeout is set to 30 sec in solr nodes.
> > > Please advise.
> >
> > The most common reason for this is general performance issues that make
> > some operations take longer than the zkClientTimeout.
> >
> > My first suspect would be long garbage collection pauses.  This assumes
> > you're not using a very recent version (4.10.x or 5.x) with the new
> > bin/solr script, and your java commandline does not have any garbage
> > collection tuning.  The bin/solr script does a lot of GC tuning.
> >
> > The second suspect would be that you don't have enough RAM left for your
> > operating system to cache your index effectively.
> >
> > It's possible to have both of these problems happening.  These problems,
> > and a few others, are outlined here:
> >
> > http://wiki.apache.org/solr/SolrPerformanceProblems
> >
> > Thanks,
> > Shawn
> >
> >
>

--001a11400532d671d60514c534e1--