[
https://issues.apache.org/jira/browse/IGNITE-9834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16644600#comment-16644600
]
ASF GitHub Bot commented on IGNITE-9834:
----------------------------------------
GitHub user avplatonov opened a pull request:
https://github.com/apache/ignite/pull/4939
IGNITE-9834: Cancel tcp-client-disco-msg-worker in normal order after
validation error
…rror
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-gg-9834
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4939.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 #4939
----
commit 6259d3e49b962b914fcc89cfdfc3002ace1ceabc
Author: Alexey Platonov <aplatonovv@...>
Date: 2018-10-10T07:53:31Z
cancel tcp-client-disco-msg-worker in normal order after validation error
----
> ClientImpl shouldn't fail JVM with 130 error code after node validation errors
> ------------------------------------------------------------------------------
>
> Key: IGNITE-9834
> URL: https://issues.apache.org/jira/browse/IGNITE-9834
> Project: Ignite
> Issue Type: Bug
> Reporter: Alexey Platonov
> Assignee: Alexey Platonov
> Priority: Major
> Labels: MakeTeamcityGreenAgain
>
> In the current number of Ignite if client (tcp-client-disco-msg-worker)
> receive validation error message represented by
> TcpDiscoveryCheckFailedMessage then client fail with 130 error code.
> Semantically such behavior is invalid. Client must cancel own work in normal
> order.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
