Re: Shard allocation across nodes

[Tom Evans]

Thank you both, those are exactly what I was looking for!

If I'm reading it right, if I specify a "-Dvmhost=foo" when starting
SolrCloud, and then specify a snitch rule like this when creating the
collection:

  sysprop.vmhost:*,replica:<2

then this would ensure that on each vmhost there is at most one
replica. I'm assuming that a shard leader and a replica are both
treated as replicas in this scenario.

Thanks

Tom

On Mon, Feb 1, 2016 at 8:34 PM, Erick Erickson  wrote:
> See the createNodeset and node parameters for the Collections API CREATE and
> ADDREPLICA commands, respectively. That's more a manual process, there's
> nothing OOB but Jeff's suggestion is sound.
>
> Best,
> Erick
>
>
>
> On Mon, Feb 1, 2016 at 11:00 AM, Jeff Wartes  wrote:
>>
>> You could write your own snitch: 
>> https://cwiki.apache.org/confluence/display/solr/Rule-based+Replica+Placement
>>
>> Or, it would be more annoying, but you can always add/remove replicas 
>> manually and juggle things yourself after you create the initial collection.
>>
>>
>>
>>
>> On 2/1/16, 8:42 AM, "Tom Evans"  wrote:
>>
>>>Hi all
>>>
>>>We're setting up a solr cloud cluster, and unfortunately some of our
>>>VMs may be physically located on the same VM host. Is there a way of
>>>ensuring that all copies of a shard are not located on the same
>>>physical server?
>>>
>>>If they do end up in that state, is there a way of rebalancing them?
>>>
>>>Cheers
>>>
>>>Tom

Re: Shard allocation across nodes

[Jeff Wartes]

You could write your own snitch: 
https://cwiki.apache.org/confluence/display/solr/Rule-based+Replica+Placement

Or, it would be more annoying, but you can always add/remove replicas manually 
and juggle things yourself after you create the initial collection.




On 2/1/16, 8:42 AM, "Tom Evans"  wrote:

>Hi all
>
>We're setting up a solr cloud cluster, and unfortunately some of our
>VMs may be physically located on the same VM host. Is there a way of
>ensuring that all copies of a shard are not located on the same
>physical server?
>
>If they do end up in that state, is there a way of rebalancing them?
>
>Cheers
>
>Tom

Shard allocation across nodes

[Tom Evans]

Hi all

We're setting up a solr cloud cluster, and unfortunately some of our
VMs may be physically located on the same VM host. Is there a way of
ensuring that all copies of a shard are not located on the same
physical server?

If they do end up in that state, is there a way of rebalancing them?

Cheers

Tom

Re: Shard allocation across nodes

[Erick Erickson]

See the createNodeset and node parameters for the Collections API CREATE and
ADDREPLICA commands, respectively. That's more a manual process, there's
nothing OOB but Jeff's suggestion is sound.

Best,
Erick



On Mon, Feb 1, 2016 at 11:00 AM, Jeff Wartes  wrote:
>
> You could write your own snitch: 
> https://cwiki.apache.org/confluence/display/solr/Rule-based+Replica+Placement
>
> Or, it would be more annoying, but you can always add/remove replicas 
> manually and juggle things yourself after you create the initial collection.
>
>
>
>
> On 2/1/16, 8:42 AM, "Tom Evans"  wrote:
>
>>Hi all
>>
>>We're setting up a solr cloud cluster, and unfortunately some of our
>>VMs may be physically located on the same VM host. Is there a way of
>>ensuring that all copies of a shard are not located on the same
>>physical server?
>>
>>If they do end up in that state, is there a way of rebalancing them?
>>
>>Cheers
>>
>>Tom