What you probably really want is to eventually migrate to 1.0 and then build 2 separate clusters (one in each AZ) and then index into them separately, and then use the tribe node (http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-tribe.html) to federate your search results across clusters.
In the meantime assuming you really want a single cluster, there's no reason why you can't use index allocation awareness to do what you want. So for example: ES.yml on zone 1 would have: node.zone: zone1 ES.yml on zone 2 would have: node.zone: zone2 Then when you create an index that you want only to go to zone 1, you will say something like (maybe just use an index template for convenience): PUT http://localhost:9200/<zone1index> { "settings": { "index.routing.allocation.include.zone": "zone1" } } And when you create an index that you want only to go to zone 2, you will say something like (maybe just use an index template for convenience): PUT http://localhost:9200/<zone2index> { "settings": { "index.routing.allocation.include.zone": "zone2" } } -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/4b8444c3-dfa3-464c-b974-ada0b09be62b%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
