[jira] [Comment Edited] (IGNITE-13051) Optimized affinity switch on baseline node left is broken for client topology and MVCC

["Maksim Timonin (Jira)" <ji...@apache.org>]

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

Maksim Timonin edited comment on IGNITE-13051 at 6/3/20, 4:47 PM:
------------------------------------------------------------------

[~ascherbakov] could you please provide commit id where tests are failing. They're working on my machine with last version of branch ignite-13003 and cherry-picked my commit

check attachments - there are pictures from my laptop


was (Author: timonin.maksim):
[~ascherbakov] could you please provide commit id where tests are failing. They're working on my machine with last version of branch ignite-13003 and cherry-picked my commit

> Optimized affinity switch on baseline node left is broken for client topology and MVCC
> --------------------------------------------------------------------------------------
>
>                 Key: IGNITE-13051
>                 URL: https://issues.apache.org/jira/browse/IGNITE-13051
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Alexey Scherbakov
>            Assignee: Maksim Timonin
>            Priority: Critical
>             Fix For: 2.9
>
>         Attachments: Снимок экрана 2020-06-03 в 19.41.53.png, Снимок экрана 2020-06-03 в 19.42.44.png
>
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> If a node contains only client cache topology with MVCC enabled, PME will hang after changes introduced in IGNITE-12617.
> Reproduced by CachePartitionLossWithRestartsTest.testPartitionLossDetectionOnClientTopology[0 false false -1] and enabled MVCC.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)