Restarting the node cleared out the problem and everything recovered.
Thanks!
On 5/21/15 5:42 AM, Ramkumar R. Aiyengar wrote:
This shouldn't happen, but if it does, there's no good way currently for
Solr to automatically fix it. There are a couple of issues being worked on
to do that currently. But till then, your best bet is to restart the node
which you expect to be the leader (you can look at ZK to see who is at the
head of the queue it maintains). If you can't figure that out, safest is to
just stop/start all nodes in sequence, and if that doesn't work, stop all
nodes and start them back one after the other.
On 21 May 2015 00:24, "Ryan Steele" <ryan.ste...@pgi.com> wrote:
My SolrCloud cluster isn't reassigning the collections leaders from downed
cores--the downed cores are still listed as the leaders. The cluster has
been in the state for a few hours and the logs continue to report "No
registered leader was found after waiting for 4000ms." Is there a way to
force it to reassign the leader?
I'm running SolrCloud 5.0.
I have 7 Solr nodes, 3 Zookeeper nodes, and 3739 collections.
Thanks,
Ryan
---------------------------------------------------------------------------------------
This email has been scanned for email related threats and delivered safely
by Mimecast.
For more information please visit http://www.mimecast.com
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
This email has been scanned for email related threats and delivered safely by
Mimecast.
For more information please visit http://www.mimecast.com
---------------------------------------------------------------------------------------
