[
https://issues.apache.org/jira/browse/IGNITE-3475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-3475:
--------------------------------
Assignee: Stan Michalak (was: Denis Magda)
> Topology aware IP finder
> ------------------------
>
> Key: IGNITE-3475
> URL: https://issues.apache.org/jira/browse/IGNITE-3475
> Project: Ignite
> Issue Type: Improvement
> Reporter: Denis Magda
> Assignee: Stan Michalak
>
> Quite often client nodes use {{TcpDiscoveryVmIpFinder}} with a predefined
> list of server nodes to which a client can connect to.
> However during the client's lifetime it can face with the situation when all
> the server nodes that were listed in his {{TcpDiscoveryVmIpFinder}} are down
> and the client won't be able to re-connect to the rest of the server nodes
> that are live but not listed in client's IP finder.
> It makes sense to update {{TcpDiscoveryVmIpFinder}} adding {{topologyAware}}
> property. If this property is set to {{true}} then the IP finder will listen
> to discovery updates and will add update its list of internal addresses with
> the newly arrived server nodes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
