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-6818) In case of incoming communication connection ping the old one if it's alive
Date Thu, 09 Nov 2017 13:15:03 GMT

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

ASF GitHub Bot commented on IGNITE-6818:

GitHub user dkarachentsev opened a pull request:


    IGNITE-6818 - Handle half open connection in communication.


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

    $ git pull https://github.com/gridgain/apache-ignite ignite-6818

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 #3010
commit e0268851579b77d916212b08d567381ede076c64
Author: dkarachentsev <dkarachentsev@gridgain.com>
Date:   2017-11-09T13:12:44Z

    IGNITE-6818 - Handle half open connection in communication.


> In case of incoming communication connection ping the old one if it's alive
> ---------------------------------------------------------------------------
>                 Key: IGNITE-6818
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6818
>             Project: Ignite
>          Issue Type: Bug
>      Security Level: Public(Viewable by anyone) 
>    Affects Versions: 2.3
>            Reporter: Dmitry Karachentsev
>            Assignee: Dmitry Karachentsev
>            Priority: Critical
>             Fix For: 2.4
> Assume the following scenario:
> 1. Client opens connection to the server.
> 2. Server checks that it is a first connection to that node and accepts it.
> 3. By some reason firewall starts rejecting client messages with TCP reset flag set.
> 4. Client closes connection, but server doesn't know about it.
> 5. Client tries connect again.
> 6. Server rejects new connection, because it already has connection to that node.
> Possible fix: on step 6 server must check old connection if it's alive by sending some
communication message and check response. If old connection is dead - close it and accept
new one.

This message was sent by Atlassian JIRA

View raw message