# What is best node configuration in 3 node **URL:** \ **Category:** Elasticsearch\ **Created:** [September 1, 2022, 6:00am UTC](https://discuss.elastic.co/t/what-is-best-node-configuration-in-3-node/313411 "2022-09-01T06:00:08Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![hyungsun\_lim](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hyungsun_lim/32/50790_2.png) [@hyungsun\_lim](https://discuss.elastic.co/u/hyungsun_lim)\ **Post date:** [September 1, 2022, 6:00am UTC](https://discuss.elastic.co/t/what-is-best-node-configuration-in-3-node/313411/1 "2022-09-01T06:00:08Z")
Hello, i have 3 nodes to operate Elasticsearch and Kibana. I have to set role node by node (master? data? ingest?) I heard that node.roles don't need to be configured in small cluster size (smaller than 3 nodes) It means that all node can be a master, data, ingest, etc... Is it right? What is best option to configure 3 node elasticsearch cluster? ---
**Author:** ![Aniket\_Pant](https://avatars.discourse-cdn.com/v4/letter/a/77aa72/32.png) [@Aniket\_Pant](https://discuss.elastic.co/u/Aniket_Pant)\ **Post date:** [September 1, 2022, 6:05am UTC](https://discuss.elastic.co/t/what-is-best-node-configuration-in-3-node/313411/2 "2022-09-01T06:05:14Z")
it can work but it depends upon your data size. By default your node performs all roles data,master,transform,ml,ingest ---
**Author:** ![hyungsun\_lim](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hyungsun_lim/32/50790_2.png) [@hyungsun\_lim](https://discuss.elastic.co/u/hyungsun_lim)\ **Post date:** [September 1, 2022, 6:13am UTC](https://discuss.elastic.co/t/what-is-best-node-configuration-in-3-node/313411/3 "2022-09-01T06:13:23Z")
If we have to store large size data in our system, what is good option? ---
**Author:** ![Aniket\_Pant](https://avatars.discourse-cdn.com/v4/letter/a/77aa72/32.png) [@Aniket\_Pant](https://discuss.elastic.co/u/Aniket_Pant)\ **Post date:** [September 1, 2022, 6:37am UTC](https://discuss.elastic.co/t/what-is-best-node-configuration-in-3-node/313411/4 "2022-09-01T06:37:21Z")
you have to make a plan like data retention period,shard strategy (if your per day data size is more than 50 gb then you have to create 2 shards for one index) you can read this [documentation](https://www.elastic.co/guide/en/elasticsearch/reference/current/size-your-shards.html). it is good to have 2 client/coordinate nodes in your elasticsearch cluster, apart from 3 nodes of elastic. ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [September 1, 2022, 6:51am UTC](https://discuss.elastic.co/t/what-is-best-node-configuration-in-3-node/313411/5 "2022-09-01T06:51:18Z")
> [@hyungsun\_lim](#): > > I heard that node.roles don't need to be configured in small cluster size (smaller than 3 nodes) Yes, that is correct. You always want to have threee master eligible nodes in the cluster and if the nodes have the same specification it makes sense to let them have all roles. > [@hyungsun\_lim](#): > > If we have to store large size data in our system, what is good option? With only three nodes the default is fine. The amount of data each node can handle will generally be driven by the amount of heap you have and how efficiently you use this and/or performance requirements. > [@Aniket\_Pant](#): > > it is good to have 2 client/coordinate nodes in your elasticsearch cluster, apart from 3 nodes of elastic. I disagree. Adding coordinating nodes can benefit, but it is very use case specific. Adding two data nodes will in my mind make a much bigger difference than adding two coordinating nodes. ---
**Author:** ![hyungsun\_lim](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hyungsun_lim/32/50790_2.png) [@hyungsun\_lim](https://discuss.elastic.co/u/hyungsun_lim)\ **Post date:** [September 1, 2022, 10:08am UTC](https://discuss.elastic.co/t/what-is-best-node-configuration-in-3-node/313411/6 "2022-09-01T10:08:04Z")
Thank you for reply. When i use three node as default, how can client access elasticsearch cluster? ``` Client I ?????? \/ Server1 Server2 Server3 ``` If i have coordinate node, client just access coordinate node IP address. However, when 3 nodes are default, how client can access es?? ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [September 1, 2022, 11:51am UTC](https://discuss.elastic.co/t/what-is-best-node-configuration-in-3-node/313411/7 "2022-09-01T11:51:30Z")
Clients typically take a list of all three nodes and can connect to any/all of them. This makes the whole setup fault tolerant. ---
**Author:** ![hyungsun\_lim](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hyungsun_lim/32/50790_2.png) [@hyungsun\_lim](https://discuss.elastic.co/u/hyungsun_lim)\ **Post date:** [September 1, 2022, 1:01pm UTC](https://discuss.elastic.co/t/what-is-best-node-configuration-in-3-node/313411/8 "2022-09-01T13:01:47Z")
Thank you for your tip!! I have another question. If i want to make access point to one, i have two choices, Load Balancer and coordinate node. In this case, what is best option? I heard that coordinate node can be load balancer, request routing, etc. Is the coordinate node good for access point for ES Cluster ?? ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [September 1, 2022, 1:08pm UTC](https://discuss.elastic.co/t/what-is-best-node-configuration-in-3-node/313411/9 "2022-09-01T13:08:45Z")
> [@hyungsun\_lim](#): > > If i want to make access point to one, i have two choices, Load Balancer and coordinate node. Why do you need a single access point? All client libraries, as well as Beats and Logstash, supports specifying multiple node addresses. If you add a client node that will be a single point of failure, which is typically what you are trying to avoid when using a cluster. If you have more than one client node for resiliency the clients need to be able to connect to all of them, and in that case they could just as well connect directly to multiple data nodes. ---
**Author:** ![hyungsun\_lim](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hyungsun_lim/32/50790_2.png) [@hyungsun\_lim](https://discuss.elastic.co/u/hyungsun_lim)\ **Post date:** [September 6, 2022, 1:35am UTC](https://discuss.elastic.co/t/what-is-best-node-configuration-in-3-node/313411/10 "2022-09-06T01:35:39Z")
Thank you for your reply ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 4, 2022, 1:36am UTC](https://discuss.elastic.co/t/what-is-best-node-configuration-in-3-node/313411/11 "2022-10-04T01:36:08Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.