Been a real joy working with es, and today I'm trying to see if I can stump
es with a tricky config.
Say I have 2 data nodes that contain a collection of indices that were set
up with number_of_shards=1 and number_of_replicas=1.
Say I want to add a data node that only contains replicas of the existing
shards. My understanding is I can spin up the new data node and then update
the indices to auto_expand_replicas=0-all and the new data node will
acquire a replica of all the existing shards.
But, my struggle is to ensure that going forward when new indices are
created that this 3rd node does not get any primary shards.
The general goal is to have a small subset of data nodes that are allowed
to get primary (and replica) shards while another subset of data nodes are
only allowed to get replica shards.
I've been wrestling with auto_expand_replicas and the
[index,cluster].routing.allocation.enable settings and can't figure out how
to make it work.
Any suggestions from the es masters out there?
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@example.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/b4459e87-4df2-4667-97a8-10bf62360d5f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.