# Coordinating node vs service Lod balancing different backends

**URL:** <https://discuss.elastic.co/t/coordinating-node-vs-service-lod-balancing-different-backends/272377>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [May 7, 2021, 7:28am UTC](https://discuss.elastic.co/t/coordinating-node-vs-service-lod-balancing-different-backends/272377 "2021-05-07T07:28:35Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![purushothamkdr143](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/purushothamkdr143/32/90242_2.png) [@purushothamkdr143](https://discuss.elastic.co/u/purushothamkdr143)\
**Post date:** [May 7, 2021, 7:28am UTC](https://discuss.elastic.co/t/coordinating-node-vs-service-lod-balancing-different-backends/272377/1 "2021-05-07T07:28:35Z")

</div>

Hi All,

I am setting up elasticsearch cluster on k8s using eck operator. we all know that service gets created ( clustername-es-http ) with all the backend endpoints as nodes(master,node etc etc). this behavior is default. However we can change this by routing traffic only to coordinating node which in turn forwards/loadbalances request to other backend nodes. So 2 approaches.

Approach 1: elasticsearch service -\> all backend nodes  
Approach 2: elasticsearch service -\> coordinating node -\> backed nodes

1. what is the benefit of going with 2 approach, as load balancing is already happening in approach-1?

2. are there any other benefits of going with approach-2?

3. If approach-2 has more benefits can I apply the same to kibana as well?

Regards,  
Purushotham Reddy. K

---

<div class="post-metadata">

**Author:** ![sebgl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sebgl/32/48702_2.png) [@sebgl](https://discuss.elastic.co/u/sebgl)\
**Post date:** [May 17, 2021, 7:42am UTC](https://discuss.elastic.co/t/coordinating-node-vs-service-lod-balancing-different-backends/272377/2 "2021-05-17T07:42:59Z")

</div>

Hi! Sorry for the late answer.

Approach 2 (dedicated service for coordinating-only nodes) has the advantage of not routing requests to dedicated master nodes, for examples, and not overload them with user-facing requests.  
Of course you need a minimum amount of coordinating-only nods to route requests efficiently. If you have a single coordinating-only node then your cluster availability and performance may depend on that single Pod.

> If approach-2 has more benefits can I apply the same to kibana as well?

As of today (ECK 1.5.0), this is rather complicated to achieve.  
Starting ECK 1.6.0 (soon!), this should be much easier, see [Traffic Splitting | Elastic Cloud on Kubernetes [master] | Elastic](https://www.elastic.co/guide/en/cloud-on-k8s/master/k8s-traffic-splitting.html#k8s-traffic-splitting-with-service-name).

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [June 14, 2021, 7:43am UTC](https://discuss.elastic.co/t/coordinating-node-vs-service-lod-balancing-different-backends/272377/3 "2021-06-14T07:43:32Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.