Thanks Anshum
On Mon, Sep 21, 2015 at 6:23 PM, Anshum Gupta
wrote:
> CloudSolrClient is thread safe and it is highly recommended you reuse the
> client.
>
> If you are providing an HttpClient instance while constructing, make sure
> that the HttpClient uses a
Thank you Anshum & Upayavira.
BTW do any of you guys know if CloudSolrClient is ThreadSafe ??
Thanks,
Ravi Kiran Bhaskar
On Monday, September 21, 2015, Anshum Gupta wrote:
> Hi Ravi,
>
> I just tried it out and here's my understanding:
>
> 1. Starting Solr with -c
CloudSolrClient is thread safe and it is highly recommended you reuse the
client.
If you are providing an HttpClient instance while constructing, make sure
that the HttpClient uses a multi-threaded connection manager.
On Mon, Sep 21, 2015 at 3:13 PM, Ravi Solr wrote:
>
Hi Ravi,
I just tried it out and here's my understanding:
1. Starting Solr with -c starts Solr in cloud mode. This is used to start
Solr with an embedded zookeeper.
2. Starting Solr with -z starts Solr in cloud mode, with the zk connection
string you specify. You don't need to explicitly specify
Can somebody kindly help me understand the difference between the following
startup calls ?
./solr start -p -s /solr/home -z zk1:2181,zk2:2181,zk3:2181
Vs
./solr start -c -p -s /solr/home -z zk1:2181,zk2:2181,zk3:2181
What happens if i don't pass the "-c" option ?? I read the
As it says below, -c enables a Zookeeper node within the same JVM as
Solr. You don't want that, as you already have an ensemble up and
running.
Upayavira
On Mon, Sep 21, 2015, at 09:35 PM, Ravi Solr wrote:
> Can somebody kindly help me understand the difference between the
> following
> startup