[
https://issues.apache.org/jira/browse/IGNITE-3152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15339719#comment-15339719
]
Anton Vinogradov commented on IGNITE-3152:
------------------------------------------
Semantic of {{ClusterNode.isClient()}} is:
{{Tests whether or not this node is connected to cluster as a client.}}
and it's properly used to detect is another node joined to server topology or
not.
{{TcpDiscoveryIpFinderAdapter.discoveryClientMode()}}
Used at joining node. Similar check used at
{{org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi#spiStart}}
So, basicly, {{TcpDiscoveryIpFinderAdapter.discoveryClientMode()}} is a cause
and {{ClusterNode.isClient()}} is an effect.
Seems both method is reqired, and both works correct.
> Client node's addresses are registered in IP finder
> ---------------------------------------------------
>
> Key: IGNITE-3152
> URL: https://issues.apache.org/jira/browse/IGNITE-3152
> Project: Ignite
> Issue Type: Bug
> Components: general
> Affects Versions: 1.5.0.final
> Reporter: Valentin Kulichenko
> Assignee: Anton Vinogradov
> Labels: important
> Fix For: 1.7
>
> Attachments: Test.java
>
>
> Currently client node register its addresses in IP finder and never
> deregisters them. Also looks like coordinator address is also not removed.
> The simple test that shows this behavior is attached.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
