[
https://issues.apache.org/jira/browse/IGNITE-13051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17138259#comment-17138259
]
Alexey Scherbakov commented on IGNITE-13051:
--------------------------------------------
[~timonin.maksim]
# Added tests do not cover the scenario introduced in
testPartitionLossDetectionOnClientTopology causing PME hang. You need to enable
free switch exchange to execute problematic code branch (baseline node left).
# The fix seems logically incorrect. The method
org.apache.ignite.internal.processors.cache.mvcc.MvccProcessor#validateCacheConfiguration
is intended to do some validation before cache start according to java doc and
throws an exception if validation has failed. After your change validation
result is totally ignored and is performed after caches start. Most probably
mvcc flag must be initialized elsewhere.
# registerCachesFuture must be reverted back to registerCachesFut according to
code style.
> 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: reproducer.patch, Снимок экрана 2020-06-03 в
> 19.41.53.png, Снимок экрана 2020-06-03 в 19.42.44.png
>
> Time Spent: 2.5h
> 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)
