# Reg: node unicast discovery + Azure VMSS

**URL:** <https://discuss.elastic.co/t/reg-node-unicast-discovery-azure-vmss/149203>\
**Category:** Elasticsearch\
**Created:** [September 19, 2018, 11:44pm UTC](https://discuss.elastic.co/t/reg-node-unicast-discovery-azure-vmss/149203 "2018-09-19T23:44:01Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Karthik\_Ramachandran](https://avatars.discourse-cdn.com/v4/letter/k/f19dbf/32.png) [@Karthik\_Ramachandran](https://discuss.elastic.co/u/Karthik_Ramachandran)\
**Post date:** [September 19, 2018, 11:44pm UTC](https://discuss.elastic.co/t/reg-node-unicast-discovery-azure-vmss/149203/1 "2018-09-19T23:44:01Z")

</div>

Trying to understand how unicast discovery will behave when using Azure VMSS.

Scenario  
Master Nodes in Azure VMSS (Say 3 nodes)

Azure VMSS is attached to Load Balancer with a Front End.

## Query

Against the setting "discovery.zen.ping.unicast.hosts", I wanted to use the Frontend IP.

1. What would happen if Azure LB forwards the ping to same node (when pinged from a given master node)? LB would work in round robin fashion. Thought of not using IPs of all the nodes (or) use static IPs, instead use the LB front-end.

2. Does it have any impact in master election process?

Thanks for clarification.

---

<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:** [October 17, 2018, 11:44pm UTC](https://discuss.elastic.co/t/reg-node-unicast-discovery-azure-vmss/149203/2 "2018-10-17T23:44:13Z")

</div>

Closed on October 17, 2018, 11:44pm UTC

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