# Issues when a node comes back after reboot on Azure

**URL:** <https://discuss.elastic.co/t/issues-when-a-node-comes-back-after-reboot-on-azure/19558>\
**Category:** Elasticsearch\
**Created:** [September 1, 2014, 3:58pm UTC](https://discuss.elastic.co/t/issues-when-a-node-comes-back-after-reboot-on-azure/19558 "2014-09-01T15:58:52Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![satishmallik](https://avatars.discourse-cdn.com/v4/letter/s/d9b06d/32.png) [@satishmallik](https://discuss.elastic.co/u/satishmallik)\
**Post date:** [September 1, 2014, 3:58pm UTC](https://discuss.elastic.co/t/issues-when-a-node-comes-back-after-reboot-on-azure/19558/1 "2014-09-01T15:58:52Z")

</div>

Hi,  
We are trying to deploy elasticsearch for our production on Azure,

I am using following settings,

discovery.zen.ping.unicast.hosts:  
["saku-es-m01","saku-es-m02","saku-es-m03"]

discovery.zen.minimum\_master\_nodes: 2

node.tag: masternode

http.enabled: false

# Fixed settings

path.data: f:/data

path.logs: f:/logs

discovery.zen.ping.multicast.enabled: false

discovery.zen.ping.timeout: 15s

discovery.zen.fd.ping\_retries: 10

discovery.zen.fd.ping\_timeout: 45s

cluster.routing.allocation.cluster\_concurrent\_rebalance: 1

we are hitting an issue when a node shutdowns and comes back after reboot,

[2014-08-27 06:47:36,172][WARN][transport.netty] [CS-NODE-M03]  
exception caught on transport layer [[id: 0x98a6ba59]], closing connection

java.nio.channels.UnresolvedAddressException

```
            at sun.nio.ch.Net.checkAddress(Net.java:127)

            at 

```

sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:613)

```
            at 

```

org.elasticsearch.common.netty.channel.socket.nio.NioClientSocketPipelineSink.connect(NioClientSocketPipelineSink.java:108)

```
            at 

```

org.elasticsearch.common.netty.channel.socket.nio.NioClientSocketPipelineSink.eventSunk(NioClientSocketPipelineSink.java:70)

```
            at 

```

org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:574)

```
            at 

```

org.elasticsearch.common.netty.channel.Channels.connect(Channels.java:634)

```
            at 

```

org.elasticsearch.common.netty.channel.AbstractChannel.connect(AbstractChannel.java:207)

```
            at 

```

org.elasticsearch.common.netty.bootstrap.ClientBootstrap.connect(ClientBootstrap.java:229)

```
            at 

```

org.elasticsearch.common.netty.bootstrap.ClientBootstrap.connect(ClientBootstrap.java:182)

```
            at 

```

org.elasticsearch.transport.netty.NettyTransport.connectToChannelsLight(NettyTransport.java:681)

```
            at 

```

org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:644)

```
            at 

```

org.elasticsearch.transport.netty.NettyTransport.connectToNodeLight(NettyTransport.java:611)

```
            at 

```

org.elasticsearch.transport.TransportService.connectToNodeLight(TransportService.java:133)

```
            at 

```

org.elasticsearch.discovery.zen.ping.unicast.UnicastZenPing$3.run(UnicastZenPing.java:279)

```
            at 

```

java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)

```
            at 

```

java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

```
            at java.lang.Thread.run(Thread.java:724)

```

We are using unicast mechanism for node discovery as you can see from our  
config. If I restart ES service on all nodes this issue goes away. So using  
names inside unicast.hosts should not be an issue.

Please do let me know your suggestions,

Regards

Satish

--  
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).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/071a3648-e803-42e1-83c3-da9a13d499e5%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/071a3648-e803-42e1-83c3-da9a13d499e5%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![ambodi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ambodi/32/10697_2.png) [@ambodi](https://discuss.elastic.co/u/ambodi)\
**Post date:** [July 4, 2016, 8:51am UTC](https://discuss.elastic.co/t/issues-when-a-node-comes-back-after-reboot-on-azure/19558/2 "2016-07-04T08:51:23Z")

</div>

I am having the same issue, did you fix it?

---

<div class="post-metadata">

**Author:** ![satishmallik](https://avatars.discourse-cdn.com/v4/letter/s/d9b06d/32.png) [@satishmallik](https://discuss.elastic.co/u/satishmallik)\
**Post date:** [July 4, 2016, 3:57pm UTC](https://discuss.elastic.co/t/issues-when-a-node-comes-back-after-reboot-on-azure/19558/3 "2016-07-04T15:57:01Z")

</div>

I remember fixing it by setting elasticsearch service to "automatic  
delayed" instead of "automatic" This makes sure name resolution has  
happened before elastic search service starts. Could you try it?

---

<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:** [July 5, 2017, 10:38pm UTC](https://discuss.elastic.co/t/issues-when-a-node-comes-back-after-reboot-on-azure/19558/4 "2017-07-05T22:38:29Z")

</div>

Closed on July 5, 2017, 10:38pm UTC