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-1025) Need to print out warning if IP finder has a lot of addresses on Windows
Date Wed, 01 Nov 2017 16:54:00 GMT

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

ASF GitHub Bot commented on IGNITE-1025:

GitHub user 1vanan opened a pull request:




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

    $ git pull https://github.com/1vanan/ignite ignite-1025

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 #2966
commit 5a44af1199a654f4737438193a5c8d061a6ef5e4
Author: ivanan <vanen31@gmail.com>
Date:   2017-10-05T07:10:44Z

    wrong ip addresses worning was added in TCPDiscoveryVmIpFinder

commit de407e2a16f22536186f7b3e4de8adbb03308a04
Author: ivanan <vanen31@gmail.com>
Date:   2017-10-05T21:41:10Z

    change some var names

commit 99b6ca29bfc953904148004518cdc7baf14c844e
Author: ivanan <vanen31@gmail.com>
Date:   2017-10-09T21:36:48Z

    remarks were taken into account

commit a55dcc1c329459a612aaf60e2877367c867caa66
Author: ivanan <vanen31@gmail.com>
Date:   2017-10-10T21:42:39Z

    fix changes 11.10.17

commit adaf649409db53cc025de7bd8d484886847f784a
Author: ivanan <vanen31@gmail.com>
Date:   2017-10-18T22:56:49Z

    added TcpDiscoveryVmIpFinderSetAddressesWarningTest

commit 17465c952f96e11584147a6828d082c867f7838b
Author: Ivan <vanen31@gmail.com>
Date:   2017-10-24T14:32:43Z

    isUnresolved instead of TcpTimeout

commit d7be15ecc8fbce57996e234573129d00912e66a2
Author: Ivan <vanen31@gmail.com>
Date:   2017-10-24T14:38:29Z

    test with single and multiports

commit 458377e35bb9f10b5a02f77645e61f98f5e749dd
Author: Ivan <vanen31@gmail.com>
Date:   2017-10-27T14:01:54Z


commit 020ca8ca9f07636bc3288f6018a3d1a94c025839
Author: Ivan <vanen31@gmail.com>
Date:   2017-10-31T13:52:46Z

    isLoggingOfWrongAddressFirst method was added, minor changes in TcpDiscoveryVmIpFinderSetAddressesWarningTest

commit 8f3faed2db05fbc75a958ca99c8d2befe688718c
Author: Ivan <vanen31@gmail.com>
Date:   2017-10-31T15:58:54Z

    fix some comments in TcpDiscoveryVmIpFinderSetAddressesWarningTest

commit b8f3effa0bff5fd6e696d5c22abb64cea17f76a3
Author: Ivan <vanen31@gmail.com>
Date:   2017-11-01T12:06:49Z

    delete obvious comment

commit cb4519dc37ec0b96b6bcde7e6a3ceba875fde374
Author: Ivan <vanen31@gmail.com>
Date:   2017-11-01T13:50:18Z

    fix style remarks

commit fb6a02fcd58619ffedbd67cc3ec609db9f34d447
Author: Ivan <vanen31@gmail.com>
Date:   2017-11-01T14:56:26Z

    rename logIfInvalidAddressAppearedFirst to logFirstInvalidAddress


> Need to print out warning if IP finder has a lot of addresses on Windows
> ------------------------------------------------------------------------
>                 Key: IGNITE-1025
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1025
>             Project: Ignite
>          Issue Type: Improvement
>          Components: general
>    Affects Versions: sprint-4
>            Reporter: Valentin Kulichenko
>            Assignee: Ivan Fedotov
>            Priority: Minor
>              Labels: Usability, newbie
> Windows OS has a known issue: when we try to connect to unavailable address, we have
to wait for socket timeout (Linux, for example, will throw an exception immediately in this
> Because of this issue node startup process can take significant amount of time if there
is a long list of addresses in IP finder. And now it looks like a node simply hangs for a
while (sometimes several minutes).
> We should print the warning in this case to tell the user that startup can take time
and make suggestions on how to avoid it.

This message was sent by Atlassian JIRA

View raw message