You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Anton Vinogradov (JIRA)" <ji...@apache.org> on 2016/06/09 15:01:21 UTC

[jira] [Comment Edited] (IGNITE-3152) Client node's addresses are registered in IP finder

    [ https://issues.apache.org/jira/browse/IGNITE-3152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15320858#comment-15320858 ] 

Anton Vinogradov edited comment on IGNITE-3152 at 6/9/16 3:00 PM:
------------------------------------------------------------------

node.isClient() checks that clientRouterNodeId != null
Which should means this client node not in forceServerMode, correct?

So, !node.isClient() will exclude only client nodes at client mode.


was (Author: avinogradov):
node.isClient() checks that clientRouterNodeId != null
Which should means this client node not in forceServerMode, correct?

So, !node.isClient() will exclude only client nodes at clietn mode.

> 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)