On 5/16/2016 6:29 PM, Li Ding wrote:
> 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
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 for restart solr w
Hi Anshum,
This is for restart solr with 1000 collections. I created an environment
with 1023 collections today All collections are empty. During repeated
restart test, one of the cores are marked as "recovering" and stuck there
for ever. The solr is 4.6.1 and we have 3 zk hosts and 8 solr hos
I think you are approaching the problem all wrong. This seems, what is
described as an x-y problem (https://people.apache.org/~hossman/#xyproblem).
Can you tell us more about :
* What's your setup like? SolrCloud - Version, number of shards, is there
any custom code, etc.
* Did you start seeing thi
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
