Awesome. This is what I was looking for. Will try these. Thanks.
On 10/1/15 1:31 PM, Shawn Heisey wrote:
On 10/1/2015 12:39 PM, Rallavagu wrote:
Thanks for the response Andrea.
Assuming that Solr has it's own thread pool, it appears that
"PoolingClientConnectionManager" has a maximum 20 thread
On 10/1/2015 12:39 PM, Rallavagu wrote:
> Thanks for the response Andrea.
>
> Assuming that Solr has it's own thread pool, it appears that
> "PoolingClientConnectionManager" has a maximum 20 threads per host as
> default. Is there a way to changes this increase to handle heavy
> update traffic? Tha
Thanks Shawn. This is good data.
On 10/1/15 11:43 AM, Shawn Heisey wrote:
On 10/1/2015 11:50 AM, Rallavagu wrote:
Solr 4.6.1, single Shard, cloud with 4 nodes
Solr is running on Tomcat configured with 200 threads for thread pool.
As Solr uses
"org.apache.http.impl.conn.PoolingClientConnectionM
On 10/1/2015 11:50 AM, Rallavagu wrote:
> Solr 4.6.1, single Shard, cloud with 4 nodes
>
> Solr is running on Tomcat configured with 200 threads for thread pool.
> As Solr uses
> "org.apache.http.impl.conn.PoolingClientConnectionManager" for
> replication, my question is does Solr threads use conne
Thanks for the response Andrea.
Assuming that Solr has it's own thread pool, it appears that
"PoolingClientConnectionManager" has a maximum 20 threads per host as
default. Is there a way to changes this increase to handle heavy update
traffic? Thanks.
On 10/1/15 11:05 AM, Andrea Gazzarini
Hi,
Maybe I could be wrong as your question is related with Solr internals (I
believe the dev list is a better candidate for such questions).
Anyway, my thoughts: unless you're within a JCA inbound component (and Solr
isn't), the JEE specs say you shouldn' start new threads. For this reason,
ther
