ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Li <david.li...@gmail.com>
Subject TcpDiscoveryVmIpFinder handle IP change
Date Mon, 14 Aug 2017 07:18:20 GMT
Hi all,

Currently I am connecting to an ignite server node
with TcpDiscoveryVmIpFinder, from a client node, using a domain as
hostname, eg. ignite.dev, normally when there is any network issue or
server issue, the client node will reconnect automatically when the network
restore or ignite server node up again. But it cannot reconnect if the IP
address of the server node has changed.

I had a look the TcpDiscoveryVmIpFinder class, when setting the address, it
resolve the ip string (or hostname) as  InetSocketAddress , I guess when
ignite try to reconnect, it directly use the  InetSocketAddress , will not
try to resolve the ip address by the original hostname, so I am thinking
maybe I can extend the TcpDiscoveryVmIpFinder, and make it work for my
scenario, but I am not very sure about the place to change.

Overall, my ignite server node may change its IP address if it up from a
failure, and I want my client node can automatically reconnect itself to
the server node. Any help are appreciated. Thank you.

14 Aug

View raw message