Dear Mark, others, Thanks for the advice! I do have some more questions I'm afraid...
On Friday, July 25, 2014 1:30:07 PM UTC+2, Mark Walkom wrote: > > I'd go with option 3, but make all 3 nodes master eligable. That way you > prevent complete loss of the cluster and protect against split brain. > Right. Is there any advantage to having the 'coordinator' be the master of the cluster? I.e., suppose I restart the coordinator and one of the data nodes becomes master, should I then somehow make the coordinator the master again? > > To change a node role just update the config and restart the service. > Shards will be auto promoted (ie replicas to primaries), but you can > disable allocation to stop this so when your other node comes up it will > just initialise the shards it has locally, this speeds up recovery. > Well, the current situation is that the shards are divided over the three nodes, each with 1 replica. So, if I change the coordinator into data=false, it will need to distribute the shards it had over the other two nodes so each node has a copy of each shard, so I need to allow allocation, right? Or should I first set # replicates to 2, so the data is copied to all nodes, before setting the coordinator to data=false? Sorry for all the questions, but this part of elastic is new to me and I'm afraid to mess up the index... Thanks, Wouter -- 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/899f5ae8-202b-4f59-9e20-5ef05148aec7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
