yes, Alex. This is reproducible. Will check if we can run Wireshark.
Thank you.
On Mon, Aug 17, 2020 at 8:11 PM Alexandre Rafalovitch
wrote:
> If this is reproducible, I would run Wireshark on the network and see what
> happens at packet level.
>
> Leaning towards firewall timing out and just s
If this is reproducible, I would run Wireshark on the network and see what
happens at packet level.
Leaning towards firewall timing out and just starting to drop all packets.
Regards,
Alex
On Mon., Aug. 17, 2020, 6:22 p.m. Susheel Kumar,
wrote:
> Thanks for the all responses.
>
> Shawn - to
Thanks for the all responses.
Shawn - to your point both ping or select in between taking 600+ seconds to
return as you can see below 1st ping attempt was all good and 2nd took long
time. Similarly for select couple of select all returned fine and then
suddenly taking long time. I'll try to run s
Hi,
How long to display the solr console ?
What about CPU and iowait with top ?
You should start by eliminate network issue between your solr nodes by
testing it with netcat on solr port.
http://deice.daug.net/netcat_speed.html
Dominique
Le ven. 14 août 2020 à 23:40, Susheel Kumar a
écrit :
>
: Saturday, August 15, 2020 7:33 AM
To: solr-user@lucene.apache.org
Subject: Re: Solr ping taking 600 seconds
On 8/14/2020 3:39 PM, Susheel Kumar wrote:
> One of our Solr 6.6.2 DR cluster (target CDCR) which even doesn't have
> any live search load seems to be taking 60 ms many ti
On 8/14/2020 3:39 PM, Susheel Kumar wrote:
One of our Solr 6.6.2 DR cluster (target CDCR) which even doesn't have any
live search load seems to be taking 60 ms many times for the ping /
health check calls. Anyone has seen this before/suggestion what could be
wrong. The collection has 8 shards
