[
https://issues.apache.org/jira/browse/IGNITE-9327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585917#comment-16585917
]
ASF GitHub Bot commented on IGNITE-9327:
----------------------------------------
GitHub user akalash opened a pull request:
https://github.com/apache/ignite/pull/4579
IGNITE-9327 stop the node if IgniteNeedReconnectException happened
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9327
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4579.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4579
----
commit aed7d76983798abb76972d92d1a8f63fa8a93762
Author: Anton Kalashnikov <kaa.dev@...>
Date: 2018-08-20T13:18:24Z
IGNITE-9327 stop the node if IgniteNeedReconnectException happened
----
> Client Nodes hangs because client reconnect not handled
> --------------------------------------------------------
>
> Key: IGNITE-9327
> URL: https://issues.apache.org/jira/browse/IGNITE-9327
> Project: Ignite
> Issue Type: Test
> Reporter: Anton Kalashnikov
> Assignee: Anton Kalashnikov
> Priority: Major
>
> Reproduced by
> IgniteCacheClientReconnectTest#testClientInForceServerModeStopsOnExchangeHistoryExhaustion
> If IgniteNeedReconnectException happend we should stop the node if reconnect
> doesn't supported. But after
> https://issues.apache.org/jira/browse/IGNITE-8673 we became to ignore this
> case.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
