There's at least two ways of going about this: 1> when you create your collection, create it with the specil "EMPTY" node set, then use ADDREPLICA to place each replica where you want it, applying your knowledge of where the VMs are hosted.
2> use the replica placement rules, see: https://lucene.apache.org/solr/guide/6_6/rule-based-replica-placement.html (but check your individual version, you can download the PDF for your version see the "Other formats" drop-down at the top if this link). What you're looking for I think is "rack awareness". Search for "rack" at the link. Best, Erick On Sun, Jun 10, 2018 at 5:25 AM, THADC <timothy.clotworthy.j...@gmail.com> wrote: > Thanks Eric, that was helpful. But what if you want to proactively replicate > across multiple servers either at the VM or even physical server level. It > seems that we have control over the zookeeper locations and the solr server > locations since we explicitly define these when we configure the instances > (at least at the port level), but for replicas, in my limited experience, we > only specify the quantity without regard to physical/logical location for > each replica. Obviously at least for HA, location is relevant if you are > trying to address physical server failure or VM failure as opposed to > application-level (higher-level) failures. > > Maybe a better question is, if I have multiple VMs that can span multiple > physical servers, how do I come up with appropriate distribution strategies > for both HA and performance? > > Thank you again! > > Tim Clotworthy > > > > -- > Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
