# Elastic Search Cluster deployment failure on Azure

**URL:** <https://discuss.elastic.co/t/elastic-search-cluster-deployment-failure-on-azure/102617>\
**Category:** Elasticsearch\
**Created:** [October 3, 2017, 9:19pm UTC](https://discuss.elastic.co/t/elastic-search-cluster-deployment-failure-on-azure/102617 "2017-10-03T21:19:16Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![rangv](https://avatars.discourse-cdn.com/v4/letter/r/e495f1/32.png) [@rangv](https://discuss.elastic.co/u/rangv)\
**Post date:** [October 3, 2017, 9:19pm UTC](https://discuss.elastic.co/t/elastic-search-cluster-deployment-failure-on-azure/102617/1 "2017-10-03T21:19:16Z")

</div>

We are seeing the following error creating ES cluster on Azure in a VNET with Express route. Cluster was deployed using azure market place : [https://azuremarketplace.microsoft.com/en-us/marketplace/apps/elastic.elasticsearch](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/elastic.elasticsearch)  
[2017-10-01T00:00:00,844][WARN][o.e.d.z.ZenDiscovery] [ABCDDdata-0] not enough master nodes discovered during pinging (found [[Candidate{node={ABCDDdata-0}{EsZQuEPFTWS9qOs2Q0-Biw}{i0ypySR1TNiCahRjbdWlzQ}{xx.xxx.xx.xx}{xx.xxx.xx.xx:9300}{ml.enabled=true}, clusterStateVersion=-1}]], but needed [2]), pinging again  
[2017-10-01T00:00:00,846][WARN][o.e.d.z.UnicastZenPing] [ABCDDdata-0] failed to resolve host [ABCDDdata-1:9300]  
java.net.UnknownHostException: ABCDDdata-1  
at java.net.InetAddress.getAllByName0(InetAddress.java:1280) ~[?:1.8.0\_144]  
at java.net.InetAddress.getAllByName(InetAddress.java:1192) ~[?:1.8.0\_144]  
at java.net.InetAddress.getAllByName(InetAddress.java:1126) ~[?:1.8.0\_144]  
at org.elasticsearch.transport.TcpTransport.parse(TcpTransport.java:921) ~[elasticsearch-5.5.1.jar:5.5.1]  
at org.elasticsearch.transport.TcpTransport.addressesFromString(TcpTransport.java:876) ~[elasticsearch-5.5.1.jar:5.5.1]  
at org.elasticsearch.transport.TransportService.addressesFromString(TransportService.java:691) ~[elasticsearch-5.5.1.jar:5.5.1]  
at org.elasticsearch.discovery.zen.UnicastZenPing.lambda$null$0(UnicastZenPing.java:212) ~[elasticsearch-5.5.1.jar:5.5.1]  
at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:1.8.0\_144]  
at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:569) [elasticsearch-5.5.1.jar:5.5.1]  
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0\_144]  
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0\_144]  
at java.lang.Thread.run(Thread.java:748) [?:1.8.0\_144]

---

<div class="post-metadata">

**Author:** ![forloop](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/forloop/32/9021_2.png) [@forloop](https://discuss.elastic.co/u/forloop)\
**Post date:** [October 4, 2017, 10:17pm UTC](https://discuss.elastic.co/t/elastic-search-cluster-deployment-failure-on-azure/102617/2 "2017-10-04T22:17:54Z")

</div>

Clusters deployed through the ARM template [use Azure DNS to perform name resolution for VMs](https://docs.microsoft.com/en-us/azure/virtual-network/virtual-networks-name-resolution-for-vms-and-role-instances), using hostnames.

If you're using ExpressRoute, I suspect you maybe using your own DNS server(s); You will need to [set these up to be able to resolve VMs in Azure by hostname](https://docs.microsoft.com/en-us/azure/virtual-network/virtual-networks-name-resolution-for-vms-and-role-instances#name-resolution-using-your-own-dns-server), in order for Elasticsearch nodes to be able to communicate with each other and form a cluster.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [November 1, 2017, 10:17pm UTC](https://discuss.elastic.co/t/elastic-search-cluster-deployment-failure-on-azure/102617/3 "2017-11-01T22:17:57Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.