This happened when the second time I'm performing restart. But after that,
every time this collection is stuck at here. If I restart the leader node
as well, the core can get out of the recovering state
On Mon, May 16, 2016 at 5:00 PM, Li Ding wrote:
> Hi Anshum,
>
> This is fo
e recently? If so, what did you change?
>
> To already answer your question, there is no way in SolrCloud to disable or
> remove the concept of 'leaders'. However, there would be other ways to fix
> your setup, and get rid of the issues you are facing once you share more
>
Hi all,
We have an unique scenario where we don't need leaders in every collection
to recover from failures. The indexing never changes. But we have faced
problems where either zk marked a core as down while the core is fine in
non-distributed query or during restart, the core never comes up. M
logs and see if you have any
> stop-the-world GC pauses that take longer than the ZK
> timeout.
>
> see Mark Millers primer on GC here:
> https://lucidworks.com/blog/2011/03/27/garbage-collection-bootcamp-1-0/
>
> Best,
> Erick
>
> On Tue, Apr 26, 2016 at 2:13 PM,
h,*
> *8328789519,*
> *If I don't answer your call please leave a voicemail with your contact
> info, *
> *will return your call ASAP.*
>
> On Thu, Apr 21, 2016 at 6:02 AM, YouPeng Yang
> wrote:
>
> > Hi
> >We have used Solr4.6 for 2 years,If you post mor
Hi All,
We are using SolrCloud 4.6.1. We have observed following behaviors
recently. A Solr node in a Solrcloud cluster is up but some of the cores
on the nodes are marked as down in Zookeeper. If the cores are parts of a
multi-sharded collection with one replica, the queries to that collectio
