ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Platonov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-9834) ClientImpl shouldn't fail JVM with 130 error code after node validation errors
Date Wed, 10 Oct 2018 11:32:00 GMT

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

Alexey Platonov commented on IGNITE-9834:
-----------------------------------------

It doesn't look like above tests was failed by my code. Maybe this is new errors.

> 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)

Mime
View raw message