[jira] [Commented] (IGNITE-9326) IgniteCacheFailedUpdateResponseTest hangs in master

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

ASF GitHub Bot commented on IGNITE-9326:
----------------------------------------

GitHub user agoncharuk opened a pull request:

    https://github.com/apache/ignite/pull/4588

    IGNITE-9326 Fixed node failure processor invocation when EntryProcess…

    …or result serialization throws an exception

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-9326

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/4588.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 #4588
    
----
commit df67c7826de826605baeb183c0007b548020756c
Author: Alexey Goncharuk <al...@...>
Date:   2018-08-21T15:06:17Z

    IGNITE-9326 Fixed node failure processor invocation when EntryProcessor result serialization throws an exception

----


> IgniteCacheFailedUpdateResponseTest hangs in master
> ---------------------------------------------------
>
>                 Key: IGNITE-9326
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9326
>             Project: Ignite
>          Issue Type: Test
>            Reporter: Alexey Goncharuk
>            Assignee: Alexey Goncharuk
>            Priority: Major
>              Labels: MakeTeamcityGreenAgain
>             Fix For: 2.7
>
>
> The test started to hang after IGNITE-8926 was merged.
> The reason is that entry processor result started to be lazily serialized during the message send, which results in a failure handler invocation. However, the test checks that the exception is rethrown to a user.
> The issue affects only ATOMIC caches.
> One of the possible fixes is to marshal the result after the topology lock is released.
> Muting test in master for now.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)