# Coordinating node for load balancing both Kibana as well as logstash **URL:** \ **Category:** Elasticsearch\ **Created:** [July 30, 2019, 8:26pm UTC](https://discuss.elastic.co/t/coordinating-node-for-load-balancing-both-kibana-as-well-as-logstash/192983 "2019-07-30T20:26:59Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![kabali12345](https://avatars.discourse-cdn.com/v4/letter/k/6a8cbe/32.png) [@kabali12345](https://discuss.elastic.co/u/kabali12345)\ **Post date:** [July 30, 2019, 8:26pm UTC](https://discuss.elastic.co/t/coordinating-node-for-load-balancing-both-kibana-as-well-as-logstash/192983/1 "2019-07-30T20:26:59Z")
Hi All... I have a cluster of 10 data/master eligible nodes, each node has 64GB of Memory and 3TB of disk. I am going to index 40GB of data daily and I have separate logstash instances of 16GB of Memory to index the data. **Now I am referring to, two types of architectures and please suggest me the best one.** In the first architecture, I will point all 10 data/master eligible nodes in logstash output elasticsearch hosts tag for load balancing. In the Second architecture, I will add two additional coordinating nodes and pointing them in logstash output elasticsearch hosts tag for load balancing. Also, I would like to add these 2 coordinating nodes to, two separate kibana instances, In order to achive high availablity and load balance for kibana as well. Please suggest me the best approach. Thank you ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 27, 2019, 8:27pm UTC](https://discuss.elastic.co/t/coordinating-node-for-load-balancing-both-kibana-as-well-as-logstash/192983/2 "2019-08-27T20:27:02Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.