No. Which copy of the shard is the replica and which is the slave can change all the time. Most actions take almost the same amount of CPU/memory/time on master as slave. If you find this not true for your workload your best bet is to fiddle with the allocation parameters and raise the weight of the one for masters. This will cause elasticsearch to tend to spread masters move evenly.
Sent from my iPhone > On Jun 1, 2014, at 8:27 AM, Tamanjit Bindra <[email protected]> wrote: > > Hi all, > We are planning to migrate from 0.90 version of ES to the latest version. > Also we are revisiting our production architecture. > > Currently we have one master and one replica of the data. Both currently are > 16G ram servers. > My question is, is it advisable to have a better configuration master sever > ie say 32G ram on master and 16G ram on a slave node? > > -- > 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/CADA%3D_UP8eFs5vgwaRB7Yiu7%2BFxpbjA6XX%3DcK4COJxUker2EaWw%40mail.gmail.com. > For more options, visit https://groups.google.com/d/optout. -- 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/00B985DD-13E9-422A-B3F6-3A7A6D5F4386%40gmail.com. For more options, visit https://groups.google.com/d/optout.
