Hi Shawn, Good to know about this configuration in shardHandler. We will try this settings and keep you posted on status. Hope setting changes will resolve the issue.
Regards, Ganesh On 06-Sep-2016 10:32 pm, "Ganesh M" <ganesh.sudhakar....@gmail.com<mailto:ganesh.sudhakar....@gmail.com>> wrote: Hi Shawn, Good to know about this configuration in shardHandler. We will try this settings and keep you posted on status. Hopefully it resolved the issue. Regards, Ganesh On 05-Sep-2016 10:02 pm, "Shawn Heisey" <apa...@elyograg.org<mailto:apa...@elyograg.org>> wrote: On 9/4/2016 10:02 PM, Ganesh M wrote: > We have captured all traffic of HTTP POST request going out from app I'm the one you've interacted with on IRC for this issue. If this index has multiple shards, one thing that might be a problem here is the ShardHandler that's internal to Solr. This is the internal HttpClient that distributes requests between Solr nodes. You may need to bump up the maxConnectionsPerHost value from its default of 20 to something larger, like 200 or 300. This goes in a shardHandlerFactory section of solr.xml. If you do not have solr.xml in zookeeper, you'll need to make this change on every Solr node. All Solr nodes will need to be restarted. https://cwiki.apache.org/confluence/display/solr/Format+of+solr.xml I hope this helps, but I cannot be certain that this is the problem. If it does fix your issue, then we might have a bug. Thanks, Shawn
