[
https://issues.apache.org/jira/browse/IGNITE-13051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17116613#comment-17116613
]
Maksim Timonin edited comment on IGNITE-13051 at 5/26/20, 10:42 AM:
--------------------------------------------------------------------
[~ascherbakov] hi! I've made some research and have a question about the test
case [0 false false -1]. In this case:
# 4 server nodes started;
# 3 of them (id is in 1,2,3) configured with IgniteConfiguration *with*
invoked setCacheConfiguration (*default* cache);
# Node with id=0 configured with IgniteConfiguration *without* invocation
setCacheConfiguration;
It looks like the id=0 node is filtered by the fact that the cache is not
configured at all, not by AttributeNodeFilter. Is it a valid case?
Please check the code line, it is not invoked for the id=0 node:
[CachePartitionLossWithRestartsTest.java#L135|https://github.com/gridgain/apache-ignite/blob/ignite-13003/modules/core/src/test/java/org/apache/ignite/internal/processors/cache/distributed/CachePartitionLossWithRestartsTest.java#L135]
After configuring the cache on the id=0 node the test case passed.
was (Author: timonin.maksim):
[~ascherbakov] hi! I've made some research and have a question about the test
case [0 false false -1]. In this case:
# 4 server nodes started;
# 3 of them (id is in 1,2,3) configured with IgniteConfiguration *with*
invoked setCacheConfiguration (*default* cache);
# Node with id=0 configured with IgniteConfiguration *without* invocation
setCacheConfiguration;
It looks like the id=0 node is filtered by the fact that the cache is not
configured at all, not by AttributeNodeFilter. Is it a valid case?
Please check the code line, it is not invoked for the id=0 node:
[CachePartitionLossWithRestartsTest.java#L135|https://github.com/gridgain/apache-ignite/blob/ignite-13003/modules/core/src/test/java/org/apache/ignite/internal/processors/cache/distributed/CachePartitionLossWithRestartsTest.java#L135]
> 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
>
>
> 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)
