Re: Question on CloudSolrServer API

2015-02-23 Thread Shalin Shekhar Mangar
By default the max connections is set to 128 and max connections per host
is 32. You can configure an HttpClient as per your needs and pass it as a
parameter to CloudSolrServer's constructor.

On Mon, Feb 23, 2015 at 3:49 PM, Manohar Sripada manohar...@gmail.com
wrote:

 Thanks for the response. How to control the number of connections pooled
 here in SolrJ Client? Also, what will be the default values for maximum
 Connections and all.

 - Thanks

 On Thu, Feb 19, 2015 at 6:09 PM, Shalin Shekhar Mangar 
 shalinman...@gmail.com wrote:

  No, you should reuse the same CloudSolrServer instance for all requests.
 It
  is a thread safe object. You could also create a static/common HttpClient
  instance and pass it to the constructor of CloudSolrServer but even if
 you
  don't, it will create one internally and use it for all requests so that
  connections can be pooled.
  On 19-Feb-2015 1:44 pm, Manohar Sripada manohar...@gmail.com wrote:
 
   Hi All,
  
   I am using CloudSolrServer API of SolrJ library from my application to
   query Solr. Here, I am creating a new connection to Solr for every
 search
   that I am doing. Once I got the results I am closing the connection.
  
   Is this the correct way? How does Solr create connections internally?
  Does
   it maintain a pool of connections (if so how to configure it)?
  
   Thanks,
   Manohar
  
 




-- 
Regards,
Shalin Shekhar Mangar.


Re: Question on CloudSolrServer API

2015-02-23 Thread Manohar Sripada
Thanks for the response. How to control the number of connections pooled
here in SolrJ Client? Also, what will be the default values for maximum
Connections and all.

- Thanks

On Thu, Feb 19, 2015 at 6:09 PM, Shalin Shekhar Mangar 
shalinman...@gmail.com wrote:

 No, you should reuse the same CloudSolrServer instance for all requests. It
 is a thread safe object. You could also create a static/common HttpClient
 instance and pass it to the constructor of CloudSolrServer but even if you
 don't, it will create one internally and use it for all requests so that
 connections can be pooled.
 On 19-Feb-2015 1:44 pm, Manohar Sripada manohar...@gmail.com wrote:

  Hi All,
 
  I am using CloudSolrServer API of SolrJ library from my application to
  query Solr. Here, I am creating a new connection to Solr for every search
  that I am doing. Once I got the results I am closing the connection.
 
  Is this the correct way? How does Solr create connections internally?
 Does
  it maintain a pool of connections (if so how to configure it)?
 
  Thanks,
  Manohar
 



Question on CloudSolrServer API

2015-02-19 Thread Manohar Sripada
Hi All,

I am using CloudSolrServer API of SolrJ library from my application to
query Solr. Here, I am creating a new connection to Solr for every search
that I am doing. Once I got the results I am closing the connection.

Is this the correct way? How does Solr create connections internally? Does
it maintain a pool of connections (if so how to configure it)?

Thanks,
Manohar


Re: Question on CloudSolrServer API

2015-02-19 Thread Shalin Shekhar Mangar
No, you should reuse the same CloudSolrServer instance for all requests. It
is a thread safe object. You could also create a static/common HttpClient
instance and pass it to the constructor of CloudSolrServer but even if you
don't, it will create one internally and use it for all requests so that
connections can be pooled.
On 19-Feb-2015 1:44 pm, Manohar Sripada manohar...@gmail.com wrote:

 Hi All,

 I am using CloudSolrServer API of SolrJ library from my application to
 query Solr. Here, I am creating a new connection to Solr for every search
 that I am doing. Once I got the results I am closing the connection.

 Is this the correct way? How does Solr create connections internally? Does
 it maintain a pool of connections (if so how to configure it)?

 Thanks,
 Manohar