otis_gospodnetic at yahoo
May 30, 2011, 5:59 PM
Post #2 of 2
Re: CLOSE_WAIT after connecting to multiple shards from a primary shard
[In reply to]
A few things:
1) why not send this to the Solr list?
2) you talk about searching, but the code sample is about optimizing the index.
3) I don't have SolrJ API in front of me, but isn't there is CommonsSolrServe
ctor that takes in a URL instead of HttpClient instance? Try that one.
Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch
Lucene ecosystem search :: http://search-lucene.com/
----- Original Message ----
> From: Mukunda Madhava <mukunda.ms [at] gmail>
> To: general [at] lucene
> Sent: Mon, May 30, 2011 1:54:07 PM
> Subject: CLOSE_WAIT after connecting to multiple shards from a primary shard
> We are having a "primary" Solr shard, and multiple "secondary" shards. We
> query data from the secondary shards by specifying the "shards" param in the
> query params.
> But we found that after recieving the data, there are large number of
> CLOSE_WAIT on the secondary shards from the primary shards.
> Like for e.g.
> tcp 1 0 primaryshardhost:56109 secondaryshardhost1:8090
> tcp 1 0 primaryshardhost:51049 secondaryshardhost1:8090
> tcp 1 0 primaryshardhost:49537 secondaryshardhost1:8089
> tcp 1 0 primaryshardhost:44109 secondaryshardhost2:8090
> tcp 1 0 primaryshardhost:32041 secondaryshardhost2:8090
> tcp 1 0 primaryshardhost:48533 secondaryshardhost2:8089
> We open the Solr connections as below..
> SimpleHttpConnectionManager cm = new
> HttpClient httpClient = new HttpClient(cm);
> solrServer = new CommonsHttpSolrServer(url,httpClient);
> But still we see these issues. Any ideas?