If it is good enough for you, it is good enough for you. I will just give you one anecdote: We implemented 3 dedicated clients on a 9 data node cluster and got a 2x performance improvement. Moving the query coordination, network io (has to receive data from every shard), and combination of results (aggs and sorts) off of the nodes providing the results is very helpful.
James On Sat, May 30, 2015 at 9:11 AM, Xudong You <xudong....@gmail.com> wrote: > Thanks Nikolas, > How do you think about dedicated "client node" (the so called load balance > node)? Any benefit of dedicated client node? Seems to me, round robin to > data nodes is good enough. > > On Friday, May 29, 2015 at 10:55:01 PM UTC+8, Nikolas Everett wrote: >> >> Dedicated master nodes are super convenient if you have the it >> infrastructure to host them on shared machines because they are very low >> load and its useful to be able to restart the master nodes quickly. We >> don't have that kind of infrastructure and our cluster is pretty large and >> not having it has bitten us once or twice but its not a huge problem. >> >> >> >> On Fri, May 29, 2015 at 10:44 AM, Xudong You <xudon...@gmail.com> wrote: >> >>> Right now we only need 4 ES nodes due to the small data volume, and all >>> 4 nodes are master & data nodes. >>> >>> Q1: >>> I am wondering in this case, is it necessary to have dedicated master >>> and client node? Any benefit of having dedicated master node? >>> >>> Some one said that dedicated master nodes (say, three master nodes) is >>> helpful to avoid the split brain issue, but even we have NO dedicated >>> master nodes, we can also avoid the split brain by setting the >>> *discovery.zen.minimum_master_nodes >>> *to a appropriate value. >>> >>> Q2: >>> Similarly, is dedicated client node really necessary in our 4 nodes >>> case? Any benefit of allocating dedicated client node? >>> >>> Thanks! >>> >>> -- >>> Please update your bookmarks! We have moved to >>> https://discuss.elastic.co/ >>> --- >>> 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 elasticsearc...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/elasticsearch/de7db788-a6d2-48c2-934b-bc5f7ae311a9%40googlegroups.com >>> <https://groups.google.com/d/msgid/elasticsearch/de7db788-a6d2-48c2-934b-bc5f7ae311a9%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- > Please update your bookmarks! We have moved to https://discuss.elastic.co/ > --- > 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 elasticsearch+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/d61afae2-2e47-4b65-866b-5a55d28b84ea%40googlegroups.com > <https://groups.google.com/d/msgid/elasticsearch/d61afae2-2e47-4b65-866b-5a55d28b84ea%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Please update your bookmarks! We have moved to https://discuss.elastic.co/ --- 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 elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAABsnTbQispJSH%3D7_wbk-W5%2BmMq1_4Yy2Mxeh8RL%2BAAYeaRx6g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
