2016 3:14 PM
To: 'solr-user@lucene.apache.org'
Subject: RE: solrcloud 6.0.1 any suggestions for fixing a replica that
stubbornly remains down
A little more information - I spotted this in the logging:
Error while trying to recover.
core=documents_
-
From: Jon Hawkesworth [mailto:jon.hawkeswo...@medquist.onmicrosoft.com]
Sent: Wednesday, August 31, 2016 2:09 PM
To: solr-user@lucene.apache.org
Subject: RE: solrcloud 6.0.1 any suggestions for fixing a replica that
stubbornly remains down
Just to follow up on this. Sorry its taken a while
ache.org
Subject: RE: solrcloud 6.0.1 any suggestions for fixing a replica that
stubbornly remains down
Thanks for your suggestion. Here's a chunk of info from the logging in the
solr admin page below. Is there somewhere else I should be looking too?
It looks to me like its stuck in a never-
Many thanks for this too, I am digging to this now.
Jon
-Original Message-
From: Erick Erickson [mailto:erickerick...@gmail.com]
Sent: Friday, August 26, 2016 5:01 PM
To: solr-user
Subject: Re: solrcloud 6.0.1 any suggestions for fixing a replica that
stubbornly remains down
OK, this
ndexFetcher
>
> File _iu0x_Lucene50_0.tip did not match. expected checksum is 3632944779
> and actual is checksum 1632973124. expected length is 325 and actual length
> is 304
>
> 8/26/2016, 6:22:12 AM
>
> WARN false
>
> IndexFetcher
>
> File segments_h7gk did not
: Thursday, August 25, 2016 10:35 PM
To: solr-user
Subject: Re: solrcloud 6.0.1 any suggestions for fixing a replica that
stubbornly remains down
This is odd. The ADDREPLICA _should_ be immediately listed as "down", but
should shortly go to "recovering"and then "active"
This is odd. The ADDREPLICA _should_ be immediately listed as "down", but
should shortly go to
"recovering"and then "active". The transition to "active" may take a while
as the index has to be
copied from the leader, but you shouldn't be stuck at "down" for very long.
Take a look at the Solr logs
Anyone got any suggestions how I can fix up my solrcloud 6.0.1 replica remains
down issue?
Today we stopped all the loading and querying, brought down all 4 solr nodes,
went into zookeeper and deleted everything under
/collections/transcribedReports/leader_initiated_recovery/shard1/ and brought
