Re: CloudServer 4.2.1 and SolrCloud 4.3.1

2014-02-20 Thread KNitin
Thanks, Shawn.


On Thu, Feb 20, 2014 at 11:29 AM, Shawn Heisey  wrote:

> On 2/20/2014 12:09 PM, KNitin wrote:
>
>>   I have a question on CloudServer client for solrcloud. How does
>> CloudServer route requests to solr?  Does it use round robin internally or
>> does it take into account any other parameter for the node (example how
>> many replicas it has, etc) ?
>>
>
> Mixing SolrJ and Solr versions when you are using CloudSolrServer and
> SolrCloud is a bad idea right now.  SolrCloud is evolving *VERY* quickly.
>  At some point in the future there will be more stability between versions,
> but right now, success is unlikely unless they are the same version.
>
> By default, CloudSolrServer in version 4.2.1 will send updates to shard
> leaders (in a round-robin fashion). For queries, it uses a full
> round-robin.  I *think* it will limit the round-robin to only nodes that
> are hosting that collection, but I'm not sure about that part.
>
> http://lucene.apache.org/solr/4_2_1/solr-solrj/org/apache/
> solr/client/solrj/impl/CloudSolrServer.html#CloudSolrServer%28java.lang.
> String,%20org.apache.solr.client.solrj.impl.LBHttpSolrServer,%20boolean%29
>
> Newer versions of CloudSolrServer (4.5.x if I remember correctly, and
> 4.6.x for sure) can route update requests directly to the leader of the
> correct shard.  It does require the same version of Solr.
>
> Thanks,
> Shawn
>
>


Re: CloudServer 4.2.1 and SolrCloud 4.3.1

2014-02-20 Thread Shawn Heisey

On 2/20/2014 12:09 PM, KNitin wrote:

  I have a question on CloudServer client for solrcloud. How does
CloudServer route requests to solr?  Does it use round robin internally or
does it take into account any other parameter for the node (example how
many replicas it has, etc) ?


Mixing SolrJ and Solr versions when you are using CloudSolrServer and 
SolrCloud is a bad idea right now.  SolrCloud is evolving *VERY* 
quickly.  At some point in the future there will be more stability 
between versions, but right now, success is unlikely unless they are the 
same version.


By default, CloudSolrServer in version 4.2.1 will send updates to shard 
leaders (in a round-robin fashion). For queries, it uses a full 
round-robin.  I *think* it will limit the round-robin to only nodes that 
are hosting that collection, but I'm not sure about that part.


http://lucene.apache.org/solr/4_2_1/solr-solrj/org/apache/solr/client/solrj/impl/CloudSolrServer.html#CloudSolrServer%28java.lang.String,%20org.apache.solr.client.solrj.impl.LBHttpSolrServer,%20boolean%29

Newer versions of CloudSolrServer (4.5.x if I remember correctly, and 
4.6.x for sure) can route update requests directly to the leader of the 
correct shard.  It does require the same version of Solr.


Thanks,
Shawn



CloudServer 4.2.1 and SolrCloud 4.3.1

2014-02-20 Thread KNitin
Hi

 I have a question on CloudServer client for solrcloud. How does
CloudServer route requests to solr?  Does it use round robin internally or
does it take into account any other parameter for the node (example how
many replicas it has, etc) ?


Thanks
Nitin