You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Dmitry Karachentsev (JIRA)" <ji...@apache.org> on 2017/01/27 08:13:25 UTC
[jira] [Assigned] (IGNITE-4473) Client should re-try connection
attempt in case of concurrent network failure
[ https://issues.apache.org/jira/browse/IGNITE-4473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmitry Karachentsev reassigned IGNITE-4473:
-------------------------------------------
Assignee: Dmitry Karachentsev
> Client should re-try connection attempt in case of concurrent network failure
> -----------------------------------------------------------------------------
>
> Key: IGNITE-4473
> URL: https://issues.apache.org/jira/browse/IGNITE-4473
> Project: Ignite
> Issue Type: Bug
> Components: general
> Affects Versions: 1.8
> Reporter: Vladimir Ozerov
> Assignee: Dmitry Karachentsev
> Fix For: 2.0
>
>
> *Problem*
> Consider the following scenario:
> 1) Client started, but there are no servers, so it hangs somewhere inside start routine.
> 2) Server appears, and discovery finishes successfully.
> 3) Nodes start talking to each other through communication SPI to finish start process (e.g. to complete exchange).
> 4) But network glitch occurs and server becomes unreachable.
> *Expected behavior*
> Client disconnects and hangs waiting for reconnect.
> *Actual behavior*
> Client throws an exception and never tries to reconnect.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)