hen this error happens.
Thanks again.
From: Shawn Heisey
Sent: Wednesday, September 18, 2019 20:21
To: solr-user@lucene.apache.org
Subject: Re: Question about "No registered leader" error
On 9/18/2019 6:11 AM, Shawn Heisey wrote:
> On 9/17/2019 9:35 PM,
Check whether the oom killer script was called. If so, there will be
log files obviously relating to that. I've seen nodes mysteriously
disappear as a result of this with no message in the regular solr
logs. If that's the case, you need to increase your heap.
Erick
On Wed, Sep 18, 2019 at 8:21
On 9/18/2019 6:11 AM, Shawn Heisey wrote:
On 9/17/2019 9:35 PM, Hongxu Ma wrote:
My questions:
* Is this error possible caused by "long gc pause"? my solr
zkClientTimeout=6
It's possible. I can't say for sure that this is the issue, but it
might be.
A followup. I was thinking
On 9/17/2019 9:35 PM, Hongxu Ma wrote:
My questions:
* Is this error possible caused by "long gc pause"? my solr
zkClientTimeout=6
It's possible. I can't say for sure that this is the issue, but it
might be.
* If so, how can I prevent this error happen? My thoughts: using
Hi all
I got an error when I was doing index operation:
"2019-09-18 02:35:44.427244 ... No registered leader was found after waiting
for 4000ms , collection: foo slice: shard2"
Beside it, there is no other error in solr log.
Collection foo have 2 shards, then I check their jvm gc log:
*
