Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAN4YXvc=E8M6SByy38MM9L+6pn8mq_vQANPMYh-x327zVS+mpA@mail.gmail.com>
References: 
 <CAFHbX1JFedm8Y9wMAnsB6Rt7YnfRTfPhnzMsyMkduROpwgpdaw@mail.gmail.com>
	<889C21C4-674F-4911-8A41-C16BF81C699C@whitepages.com>
	<CAN4YXvc=E8M6SByy38MM9L+6pn8mq_vQANPMYh-x327zVS+mpA@mail.gmail.com>
Date: Tue, 2 Feb 2016 14:21:04 +0000
Message-ID: 
 <CAFHbX1Kf8oq4h+MePc6z0_m9-6HvP2wtbR-z7Ubki0O54jJcAw@mail.gmail.com>
Subject: Re: Shard allocation across nodes
From: Tom Evans <tevans.uk@googlemail.com>
To: solr-user@lucene.apache.org
Content-Type: text/plain; charset=UTF-8

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 <erickerickson@gmail.com> 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 <jwartes@whitepages.com> 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" <tevans.uk@googlemail.com> 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