ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-4577) Ensure that certain interface addresses can be excluded form node attributes
Date Tue, 28 Mar 2017 12:15:41 GMT

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

ASF GitHub Bot commented on IGNITE-4577:

GitHub user tledkov-gridgain opened a pull request:


    IGNITE-4577: fix javadoc


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-fix-cache-javadoc

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1683
commit 98afb3721b5fb23210f827dd3e47074ad631361e
Author: tledkov-gridgain <tledkov@gridgain.com>
Date:   2017-03-28T12:13:48Z

    IGNITE-4577: fix javadoc


> Ensure that certain interface addresses can be excluded form node attributes
> ----------------------------------------------------------------------------
>                 Key: IGNITE-4577
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4577
>             Project: Ignite
>          Issue Type: Task
>          Components: general
>    Affects Versions: 1.8
>            Reporter: Vladimir Ozerov
>            Assignee: Evgenii Zhuravlev
>             Fix For: 2.0
> *Problem*
> Consider a case when node has some network interface which is not accessible from the
outside (e.g. in Docker container). Ignite adds this address to attributes, which are shared
with other nodes. Now if remote want to communicate with local node chances that he will try
to establish connection with invalid address. 
> In the worst case connection will be impossible. We use {{AddressResolver}} to handle
this situation.
> However, it appears that {{AddressResolver}} cannot prevent certain address to appear
in address list. As a result users may experience communication delays as we establish peer-to-peer
connection in one thread, iterating over all available addresses.
> *Proposed solution*
> We need to examine what happens when address resolver is set. May be it is necessary
to rethink how we handle returned object. E.g. {{null}} or empty collection might mean that
this address should not be included into the list of address. However, it may break existing
applications, so chances that other solution is needed.

This message was sent by Atlassian JIRA

View raw message