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-6474) Non-collocated IgniteSet stores duplicate values
Date Wed, 27 Jun 2018 14:28:00 GMT

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

Pavel Pereslegin updated IGNITE-6474:
-------------------------------------
    Attachment: Reproducer.java

> Non-collocated IgniteSet stores duplicate values 
> -------------------------------------------------
>
>                 Key: IGNITE-6474
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6474
>             Project: Ignite
>          Issue Type: Bug
>          Components: data structures
>    Affects Versions: 2.1
>         Environment: a ignite cluster with 2 nodes
>            Reporter: DL Ren
>            Priority: Major
>         Attachments: Reproducer.java
>
>
> Non-collocated IgniteSet shows multiple instances of the same objects when populated
from different nodes.
> This code, when run twice on different nodes, results in more than 10 elements in set:
> {code:java}
> CollectionConfiguration setCfg = new CollectionConfiguration();
> setCfg.setCacheMode(PARTITIONED);
> IgniteSet<Integer> set = ignite.set("set", setCfg);
> System.out.println("Set size before init: " + set.size());
> for (int j = 0; j < 10; j++) {
>     set.add(j);
>     System.out.println(new ArrayList<>(set));
> }
> System.out.println("Set size after init: " + set.size());
> {code}
> Collocated set seems to work as expected. Populating from one node also doesn't create
duplicates.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message