[
https://issues.apache.org/jira/browse/IGNITE-9155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16565191#comment-16565191
]
ASF GitHub Bot commented on IGNITE-9155:
----------------------------------------
GitHub user ilantukh opened a pull request:
https://github.com/apache/ignite/pull/4467
IGNITE-9155 : ExchangeFuture will not complete with Exception on state
change failure.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9155
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4467.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 #4467
----
commit 490266417bdbd97c43ed74341a20f9b8fc2d1a77
Author: Ilya Lantukh <ilantukh@...>
Date: 2018-06-09T14:59:38Z
IGNITE-9155 : ExchangeFuture will not complete with Exception on state
change failure.
----
> Exception during cluster state change terminates ExchangeWorker
> ---------------------------------------------------------------
>
> Key: IGNITE-9155
> URL: https://issues.apache.org/jira/browse/IGNITE-9155
> Project: Ignite
> Issue Type: Bug
> Reporter: Ilya Lantukh
> Assignee: Ilya Lantukh
> Priority: Major
>
> After IGNITE-8311 we throw an exception in ExchangeFuture instead swallowing
> it.
> ClusterStateChangeProcessor has it's own exception handling mechanism, which
> doesn't require ExchangeWorker termination (and leaving node in broken state).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
