Thanks Steve,
I saw this option but it will mean a bit of re-working our automation to
implement.
The documentation talks about an EC2Snitch. I wish it worked like Cassandra
where you just say that's the one you're using and it figures out how to
replicate the data
On 9/21/18, 2:40 PM, "Steve Rowe" <sar...@gmail.com> wrote:
Hi Chuck,
One way to do it is to set a system property on the JVM running each Solr
node, corresponding to the the AWS availability zone on which the node is
hosted.
For example, you could use sysprop “AWSAZ”, then use rules like:
replica:<2,sysprop.AWSAZ:us-east-1
replica:<2,sysprop.AWSAZ:us-west-1
replica:<2,sysprop.AWSAZ:ca-central-1
--
Steve
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.lucidworks.com&d=DwIFaQ&c=kKqjBR9KKWaWpMhASkPbOg&r=J-2s3b-3-OTA0o6bGDhJXAQlB5Y3s4rOUxlh_78DJl0&m=glt-Kw4TwOAGYMt6NB7R6qMysuNssE_CjJH46rL4tqo&s=6CzANqo-EwE1nnzHaTwr71MxQd7-im366kZUXznMKC8&e=
> On Sep 21, 2018, at 4:07 PM, Chuck Reynolds <creyno...@ancestry.com>
wrote:
>
> I'm using Solr 6.6 and I want to create a 90 node cluster with a
replication
> factor of three. I'm using AWS EC2 instances and I have a requirement to
> replicate the data into 3 AWS availability zones.
>
> So 30 servers in each zone and I don't see a create collection rule that
> will put one replica in each of the three zones.
>
> What am I missing?
>
>
>
> --
> Sent from:
https://urldefense.proofpoint.com/v2/url?u=http-3A__lucene.472066.n3.nabble.com_Solr-2DUser-2Df472068.html&d=DwIFaQ&c=kKqjBR9KKWaWpMhASkPbOg&r=J-2s3b-3-OTA0o6bGDhJXAQlB5Y3s4rOUxlh_78DJl0&m=glt-Kw4TwOAGYMt6NB7R6qMysuNssE_CjJH46rL4tqo&s=pnPq-r9xSpo7DZsgF-XgR0MyUIFNcaZpAI-xcX4HjCY&e=
