# When is best practice to use an ES node as HTTP only? **URL:** \ **Category:** Elasticsearch\ **Created:** [October 27, 2013, 9:41am UTC](https://discuss.elastic.co/t/when-is-best-practice-to-use-an-es-node-as-http-only/14126 "2013-10-27T09:41:54Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![dantuff](https://avatars.discourse-cdn.com/v4/letter/d/e79b87/32.png) [@dantuff](https://discuss.elastic.co/u/dantuff)\ **Post date:** [October 27, 2013, 9:41am UTC](https://discuss.elastic.co/t/when-is-best-practice-to-use-an-es-node-as-http-only/14126/1 "2013-10-27T09:41:54Z")
I'll have 5 ES nodes in my cluster, at this time I do not know how many documents we are going to have or what the average queries per second will be as we haven't go live yet. Should I set up one of the nodes as a HTTP node to take some of the processing load of the data nodes or will having a cluster of 5 data nodes (i.e. no HTTP nodes) be sufficient to handle the processing plus indexing and searching? -- 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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [October 27, 2013, 11:18am UTC](https://discuss.elastic.co/t/when-is-best-practice-to-use-an-es-node-as-http-only/14126/2 "2013-10-27T11:18:50Z")
Will you use clients with HTTP access only? And how many parallel HTTP client accesses do you want to allow? Jörg -- 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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![dantuff](https://avatars.discourse-cdn.com/v4/letter/d/e79b87/32.png) [@dantuff](https://discuss.elastic.co/u/dantuff)\ **Post date:** [October 27, 2013, 1:42pm UTC](https://discuss.elastic.co/t/when-is-best-practice-to-use-an-es-node-as-http-only/14126/3 "2013-10-27T13:42:12Z")
Thanks for your response. The plan is to use two HTTP access only clients in parallel. -- 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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [October 27, 2013, 1:56pm UTC](https://discuss.elastic.co/t/when-is-best-practice-to-use-an-es-node-as-http-only/14126/4 "2013-10-27T13:56:31Z")
If you will access with two clients only, there is almost no need in preparing extra nodes for them. Criteria for setting up HTTP proxy nodes are massive parallel HTTP accesses (a few hundred requests in parallel) and large result sets, which can legitimate a separation of index/search data nodes from proxy nodes for HTTP traffic handling and response generation phase. Jörg -- 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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![dantuff](https://avatars.discourse-cdn.com/v4/letter/d/e79b87/32.png) [@dantuff](https://discuss.elastic.co/u/dantuff)\ **Post date:** [October 28, 2013, 8:43am UTC](https://discuss.elastic.co/t/when-is-best-practice-to-use-an-es-node-as-http-only/14126/5 "2013-10-28T08:43:46Z")
If I have 5 ES nodes in my cluster which ES node should should my clients point to, the master node? If the master node goes down and a new one is elected how will my client communicate with Elasticsearch, they will still be pointing the the node that is down? On Sunday, October 27, 2013 1:56:31 PM UTC, Jörg Prante wrote: > If you will access with two clients only, there is almost no need in > preparing extra nodes for them. > > Criteria for setting up HTTP proxy nodes are massive parallel HTTP > accesses (a few hundred requests in parallel) and large result sets, which > can legitimate a separation of index/search data nodes from proxy nodes for > HTTP traffic handling and response generation phase. > > Jörg -- 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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [October 28, 2013, 8:49am UTC](https://discuss.elastic.co/t/when-is-best-practice-to-use-an-es-node-as-http-only/14126/6 "2013-10-28T08:49:14Z")
You can handle that with a load balancer, in your app, or use DNS round robin or something similar. There's nothing native to ES that'll handle it. Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) web: [www.campaignmonitor.com](http://www.campaignmonitor.com) On 28 October 2013 19:43, dan [dan.tuffery@gmail.com](mailto:dan.tuffery@gmail.com) wrote: > If I have 5 ES nodes in my cluster which ES node should should my clients > point to, the master node? If the master node goes down and a new one is > elected how will my client communicate with Elasticsearch, they will still > be pointing the the node that is down? > > On Sunday, October 27, 2013 1:56:31 PM UTC, Jörg Prante wrote: > > > If you will access with two clients only, there is almost no need in > > preparing extra nodes for them. > > > > Criteria for setting up HTTP proxy nodes are massive parallel HTTP > > accesses (a few hundred requests in parallel) and large result sets, which > > can legitimate a separation of index/search data nodes from proxy nodes for > > HTTP traffic handling and response generation phase. > > > > Jörg > > > > -- > > 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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- 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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [October 28, 2013, 11:02am UTC](https://discuss.elastic.co/t/when-is-best-practice-to-use-an-es-node-as-http-only/14126/7 "2013-10-28T11:02:25Z")
With the standard Elasticsearch clients [http://www.elasticsearch.org/blog/unleash-the-clients-ruby-python-php-perl/node](http://www.elasticsearch.org/blog/unleash-the-clients-ruby-python-php-perl/node) failover is fully supported. You can either 'sniff' a cluster for active nodes, or you can pass a list of node IPs to connect to. If a node fails, it will be sorted out from the connection list. Jörg -- 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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 2:10am UTC](https://discuss.elastic.co/t/when-is-best-practice-to-use-an-es-node-as-http-only/14126/8 "2017-07-06T02:10:15Z")