I'm not a JVM nor kernel expert so take this with a pinch of salt... my
guess woule be:
Having more CLOSE_WAIT connections can *probably* affect you in two ways:
1. Longer GC Cycles pauses (not sure how much of the connection the JVM
handles)
2. Some of the connections might be put on the tcp-ba
Hi Jacques,
Thank you for your reply. I'll give these parameters a try and report back.
Do you think having higher number of CLOSE_WAIT connections affects the
over all search delivery speed?
Regards,
Niraj
On Tue, Feb 23, 2016 at 2:57 PM, Jacques du Rand
wrote:
> Try to fiddle with your tcp s
Try to fiddle with your tcp settings:
/etc/sysctl.conf
net.ipv4.tcp_fin_timeout = 30
net.ipv4.tcp_keepalive_intvl = 2
net.ipv4.tcp_keepalive_probes = 2
net.ipv4.tcp_keepalive_time = 180
That should help.
On 23 February 2016 at 07:13, Niraj Aswani wrote:
> Hi,
>
> I am on solr 4.8.1 and runni
Hi,
I am on solr 4.8.1 and running master-slave setup with lots of cores (>3K).
Internally I maintain an instance of HTTPSolrServer for each core that is
reused for querying the respective cores. A request is received by an
intermediary tomcat and forwarded to another tomcat running Solr.
Over th
