# Setting up Elasticsearch in Production **URL:** \ **Category:** Elasticsearch\ **Created:** [February 17, 2017, 12:23am UTC](https://discuss.elastic.co/t/setting-up-elasticsearch-in-production/75417 "2017-02-17T00:23:08Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![niraj\_kumar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/niraj_kumar/32/4130_2.png) [@niraj\_kumar](https://discuss.elastic.co/u/niraj_kumar)\ **Post date:** [February 17, 2017, 12:23am UTC](https://discuss.elastic.co/t/setting-up-elasticsearch-in-production/75417/1 "2017-02-17T00:23:08Z")
Hello All, I am setting up ES in production with a different approach. I am actually splitting up the node role( master, data & ingest ). I know the configuration for each of them and this is well defined in the documentation. What makes me confuse is the how these three (master, node & ingest) node talk to each other. I have a total of 9 server ( 3 servers each ). Do i need to specify discovery.zen.ping.unicast.hosts to have FQDN's of all 9 servers? Or there is some other way or a best practices document to setup Elasticsearch with this type of approach. If someone can help me point to a documentation it would be really helpful. Thanks in advance. -- Niraj ---
**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:** [February 17, 2017, 12:24am UTC](https://discuss.elastic.co/t/setting-up-elasticsearch-in-production/75417/2 "2017-02-17T00:24:51Z")
Just list the masters in there and you will be ok. ---
**Author:** ![niraj\_kumar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/niraj_kumar/32/4130_2.png) [@niraj\_kumar](https://discuss.elastic.co/u/niraj_kumar)\ **Post date:** [February 17, 2017, 12:39am UTC](https://discuss.elastic.co/t/setting-up-elasticsearch-in-production/75417/3 "2017-02-17T00:39:43Z")
Thanks mark for the answer. But i am bit confused as, if i just list the masters in there, how it is gonna know about client and data nodes. And similarly how does data and client node know about each other. -- Niraj ---
**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:** [February 17, 2017, 1:18am UTC](https://discuss.elastic.co/t/setting-up-elasticsearch-in-production/75417/4 "2017-02-17T01:18:00Z")
Because each node will contact that list and the master will then it will tell that node about the rest of the cluster. ---
**Author:** ![niraj\_kumar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/niraj_kumar/32/4130_2.png) [@niraj\_kumar](https://discuss.elastic.co/u/niraj_kumar)\ **Post date:** [February 17, 2017, 5:38pm UTC](https://discuss.elastic.co/t/setting-up-elasticsearch-in-production/75417/5 "2017-02-17T17:38:44Z")
Now i get it 🙂 . And should i point my load balancer to client nodes instead of master. ? ---
**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:** [February 17, 2017, 9:39pm UTC](https://discuss.elastic.co/t/setting-up-elasticsearch-in-production/75417/6 "2017-02-17T21:39:06Z")
100% yes 🙂 ---
**Author:** ![niraj\_kumar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/niraj_kumar/32/4130_2.png) [@niraj\_kumar](https://discuss.elastic.co/u/niraj_kumar)\ **Post date:** [February 19, 2017, 4:10am UTC](https://discuss.elastic.co/t/setting-up-elasticsearch-in-production/75417/7 "2017-02-19T04:10:31Z")
Thanks Mark it works like a charm..... Appreciate the response and the great work elastic is doing. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 19, 2017, 4:11am UTC](https://discuss.elastic.co/t/setting-up-elasticsearch-in-production/75417/8 "2017-03-19T04:11:03Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.