lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erick Erickson <erickerick...@gmail.com>
Subject Re: Collection shard name
Date Thu, 15 Jan 2015 20:24:58 GMT
By definition, all replicas in a shard should be identical. So Solr is
doing exactly what I'd expect since you've created two nodes each
belonging to shard1 because of this parameter: "shard=shard1" so
updates will go to both exactly as they should. The name parameter
will allow you to distinguish between separates replicas of the _same_
shard.

I'd actually recommend that you don't use the admin/cores API at all
for collections and use the collections API instead, see:
https://cwiki.apache.org/confluence/display/solr/Collections+API. Note
that in the upper-left you can download the full PDF for 4.10.

Best,
Erick

On Thu, Jan 15, 2015 at 12:12 PM, kuttan palliyalil
<pklic@yahoo.com.invalid> wrote:
> Erick & Shawn,
> I am using Solr 4.10.2.
> Here is the create command,  keeping the shard=<shard1> same and changing the name=<different
folder>
> http://'<host1>'/solr/admin/cores?action=CREATE&name=shard1_1&collection=collectionName&shard=shard1&collection.configName=collconf'http://'<host2>'/solr/admin/cores?action=CREATE&name=shard1_2&collection=collectionName&shard=shard1&collection.configName=collconf'
> RegardsRajesh
>
>      On Thursday, January 15, 2015 3:01 PM, Shawn Heisey <apache@elyograg.org>
wrote:
>
>
>  On 1/15/2015 12:24 PM, Erick Erickson wrote:
>> How do you get all the shards named identically in the first place?
>
> What I have always heard is that this is what Solr 4.0.0 did when
> creating a collection -- all the cores ended up with the same name as
> the collection.  I have never used 4.0.0, so I cannot claim any
> first-hand knowledge.  Supporting more than one shard per node would not
> be possible with that naming method.
>
> Thanks,
> Shawn
>
>
>
>

Mime
View raw message