lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Damien Kamerman <dami...@gmail.com>
Subject Re: solr cloud does not start with many collections
Date Wed, 04 Mar 2015 02:08:34 GMT
After one minute from startup I sometimes see the
'org.apache.solr.cloud.ZkController; Timed out waiting to see all nodes
published as DOWN in our cluster state.'
And I see the 'Still seeing conflicting information about the leader of
shard' after about 5 minutes.
Thanks Shawn, I will create an issue.

On 4 March 2015 at 01:10, Shawn Heisey <apache@elyograg.org> wrote:

> On 3/3/2015 6:55 AM, Shawn Heisey wrote:
> > With a longer zkClientTimeout, does the failure happen on a later
> > collection?  I had hoped that it would solve the problem, but I'm
> > curious about whether it was able to load more collections before it
> > finally died, or whether it made no difference... and whether the
> > message now indicates 40 seconds or if it still says 30.
>
> I have found the code that produces the message, and the wait for this
> particular section is hardcoded to 30 seconds.  That means the timeout
> won't affect it.
>
> If you move the Solr log so it creates a new one from startup, how long
> does it take after startup begins before you see the failure that
> indicates the conflicting leader information hasn't resolved?
>
> This most likely is a bug ... our SolrCloud experts will need to
> investigate to find it, so we need as much information as you can provide.
>
> Thanks,
> Shawn
>
>


-- 
Damien Kamerman

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message