# What is the typical way to scale out the coordinating-only-node? **URL:** \ **Category:** Kibana\ **Created:** [May 7, 2018, 10:15am UTC](https://discuss.elastic.co/t/what-is-the-typical-way-to-scale-out-the-coordinating-only-node/130809 "2018-05-07T10:15:58Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![YuWatanabe](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yuwatanabe/32/13259_2.png) [@YuWatanabe](https://discuss.elastic.co/u/YuWatanabe)\ **Post date:** [May 7, 2018, 10:15am UTC](https://discuss.elastic.co/t/what-is-the-typical-way-to-scale-out-the-coordinating-only-node/130809/1 "2018-05-07T10:15:58Z")
Hello. I would like to get advice for setting up multiple coordinating only nodes when using with kibana . I have read below document in advance of asking this question. [https://www.elastic.co/guide/en/kibana/6.2/production.html#load-balancing](https://www.elastic.co/guide/en/kibana/6.2/production.html#load-balancing) I am assuming case where you use _coordinating only node_ for _cross cluster search client_ as well . Cases when increasing nodes will be large _heap usage_ because of increased amount of _user sessions_ and _aggregations_ . Do you usually _add load balancer in front of kibana and increase the set of kibana and coordinatin-only-node_ , or _add loadbalancer beneath kibana and add multiple coordinating-only-node_ ? Any recommended architecture for setting _multiple coordinating-only-nodes_? ---
**Author:** ![Nathan\_Reese](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nathan_reese/32/84829_2.png) [@Nathan\_Reese](https://discuss.elastic.co/u/Nathan_Reese)\ **Post date:** [May 7, 2018, 3:41pm UTC](https://discuss.elastic.co/t/what-is-the-typical-way-to-scale-out-the-coordinating-only-node/130809/2 "2018-05-07T15:41:33Z")
The usual architecture is to add load balancer in front of kibana and increase the set of kibana and coordinatin-only-node. ---
**Author:** ![YuWatanabe](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yuwatanabe/32/13259_2.png) [@YuWatanabe](https://discuss.elastic.co/u/YuWatanabe)\ **Post date:** [May 8, 2018, 12:45am UTC](https://discuss.elastic.co/t/what-is-the-typical-way-to-scale-out-the-coordinating-only-node/130809/3 "2018-05-08T00:45:12Z")
@Nathan_Reese Thank you for the reply. Looks cool . I will proceed testing in my lab. If my understanding is correct, both kibana will point to the same index (_kibana.index_) which is _.kibana_. Am I correct? [https://www.elastic.co/guide/en/kibana/current/settings.html](https://www.elastic.co/guide/en/kibana/current/settings.html) Also , for future reference , I found the perfect blog which describes reply from @Nathan_Reese . **Kibana High Availability** > **[Scaling Elasticsearch, Kibana, Beats, and Logstash](https://www.elastic.co/blog/small-medium-or-large-scaling-elasticsearch-and-evolving-the-elastic-stack-to-fit)** > > From proof-of-concept to production, scaling the Elastic Stack (Elasticsearch, Kibana, Beats, and Logstas) made easy. ---
**Author:** ![Nathan\_Reese](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nathan_reese/32/84829_2.png) [@Nathan\_Reese](https://discuss.elastic.co/u/Nathan_Reese)\ **Post date:** [May 8, 2018, 1:13pm UTC](https://discuss.elastic.co/t/what-is-the-typical-way-to-scale-out-the-coordinating-only-node/130809/4 "2018-05-08T13:13:43Z")
Yes, all kibana instances should point to the same kibana.index ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 5, 2018, 1:13pm UTC](https://discuss.elastic.co/t/what-is-the-typical-way-to-scale-out-the-coordinating-only-node/130809/5 "2018-06-05T13:13:44Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.