# Pulling the host names dynamically for unicast **URL:** \ **Category:** Elasticsearch\ **Created:** [October 8, 2013, 7:31pm UTC](https://discuss.elastic.co/t/pulling-the-host-names-dynamically-for-unicast/13879 "2013-10-08T19:31:45Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Amit\_Soni](https://avatars.discourse-cdn.com/v4/letter/a/c0e974/32.png) [@Amit\_Soni](https://discuss.elastic.co/u/Amit_Soni)\ **Post date:** [October 8, 2013, 7:31pm UTC](https://discuss.elastic.co/t/pulling-the-host-names-dynamically-for-unicast/13879/1 "2013-10-08T19:31:45Z")
Hi everyone - I have a deployment related question. We are planning a deployment model wherein the number of data nodes in an elastic search cluster can be reduced or increased based on the projected load in a given season. Given that we use unicast for node discovery, we need to maintain a right list of nodes in the config file. I understand that one doesn't need to have ALL the nodes listed but we are hoping that we list the nodes as accurately as we possibly can. Question I have is: Does elastic search deployment support a deployment wherein the list of (unicast) nodes in the cluster can be pulled from a centralized service? -Amit. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [October 8, 2013, 8:09pm UTC](https://discuss.elastic.co/t/pulling-the-host-names-dynamically-for-unicast/13879/2 "2013-10-08T20:09:56Z")
I think you should write a plugin for it. Have a look at what we've done in Google Compute Engine plugin: [GitHub - elastic/elasticsearch-cloud-gce: Google Compute Engine Cloud plugin for Elasticsearch](https://github.com/elasticsearch/elasticsearch-cloud-gce) Basically, implement your own implementation of [https://github.com/elasticsearch/elasticsearch-cloud-gce/blob/master/src/main/java/org/elasticsearch/cloud/gce/GceComputeServiceImpl.java](https://github.com/elasticsearch/elasticsearch-cloud-gce/blob/master/src/main/java/org/elasticsearch/cloud/gce/GceComputeServiceImpl.java) HTH -- David 😉 Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs Le 8 oct. 2013 à 21:31, Amit Soni [amitsoni29@gmail.com](mailto:amitsoni29@gmail.com) a écrit : > Hi everyone - I have a deployment related question. We are planning a deployment model wherein the number of data nodes in an Elasticsearch cluster can be reduced or increased based on the projected load in a given season. Given that we use unicast for node discovery, we need to maintain a right list of nodes in the config file. I understand that one doesn't need to have ALL the nodes listed but we are hoping that we list the nodes as accurately as we possibly can. > > Question I have is: Does Elasticsearch deployment support a deployment wherein the list of (unicast) nodes in the cluster can be pulled from a centralized service? > > ## -Amit. > > You received this message because you are subscribed to the Google Groups "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 2:13am UTC](https://discuss.elastic.co/t/pulling-the-host-names-dynamically-for-unicast/13879/3 "2017-07-06T02:13:16Z")