[ https://issues.apache.org/jira/browse/IGNITE-9442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16684865#comment-16684865 ]
Pavel Pereslegin commented on IGNITE-9442: ------------------------------------------ [~avinogradov], I merged with master branch and updated the test results, please review. > Collocated IgniteSet#close is not working on non-affinity node. > --------------------------------------------------------------- > > Key: IGNITE-9442 > URL: https://issues.apache.org/jira/browse/IGNITE-9442 > Project: Ignite > Issue Type: Bug > Components: data structures > Affects Versions: 2.6 > Reporter: Pavel Pereslegin > Assignee: Pavel Pereslegin > Priority: Major > Attachments: Reproducer.java > > > Method {{close()}} in collocated {{IgniteSet}} works incorrectly if cluster > contains non-affinity nodes. > Steps to reproduce: > 1. Start cluster with two nodes: server and client. > 2. Create collocated {{IgniteSet}} on client node. > 3. Close {{IgniteSet}} on client node. > 4. Invoke {{add()}} method on closed IgniteSet. > Expected: {{add()}} throws {{IllegalStateException}}. > Actual: {{add()}} does not throw exception and put new "orphan" item in the > datastructure cache. > Alternatively to client node we can exclude server node by using cache node > filter, as shown in attached junit reproducer. > This bug is related to > [IGNITE-6346|https://issues.apache.org/jira/browse/IGNITE-6346], which also > affects usage of IgniteSet in cluster with non-affinity nodes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)