ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Pereslegin (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-9442) Collocated IgniteSet#close is not working on non-affinity node.
Date Fri, 14 Sep 2018 08:55:00 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-9442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Pavel Pereslegin updated IGNITE-9442:
-------------------------------------
    Description: 
Method {{close()}} in collocated {{IgniteSet}} works incorrectly if cluster includes 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 relates to [IGNITE-6346|https://issues.apache.org/jira/browse/IGNITE-6346], which
also affects usage of IgniteSet in cluster with non-affinity nodes.

  was:
Method {{close()}} in collocated {{IgniteSet}} works incorrectly if cluster includes 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 throws exception and puts new "orphan" element in datastructure
cache.

Alternatively to client node we can exclude server node by using cache node filter, as shown
in attached junit reproducer.

This bug relates to [IGNITE-6346|https://issues.apache.org/jira/browse/IGNITE-6346], which
also affects usage of IgniteSet in cluster with non-affinity nodes.


> 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 includes
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 relates 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)

Mime
View raw message