Re: CLOSE_WAIT after connecting to multiple shards from a primary shard

2012-01-23 Thread Mikhail Khludnev
Hello, AFAIK by setting connectionManager.closeIdleConnections(0L); you preventing your http connecitons from caching aka disabling keep-alive. If you increase it enough you won't see many CLOSE_WAIT connections. Some explanation and solution for jdk's http client (URL Connection), not for your

Re: CLOSE_WAIT after connecting to multiple shards from a primary shard

2012-01-23 Thread Ranveer
Hi Mukund, Since I am getting this issue for long time, I had done some hit and run. In my case I am connecting the local tomcat server using solrJ. SolrJ has max connection perhost 20 and per client 2. As I have heavy load and lots of dependency on solr so it seems very low. To increase the

Re: CLOSE_WAIT after connecting to multiple shards from a primary shard

2011-06-01 Thread Mukunda Madhava
Hi Otis, Sending to solr-user mailing list. We see this CLOSE_WAIT connections even when i do a simple http request via curl, that is, even when i do a simple curl using a primary and secondary shard query, like for e.g. curl " http://primaryshardhost:8180/solr/core0/select?q=*%3A*&shards=seconda