[IGNITE-6474] Non-collocated IgniteSet stores duplicate values

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.1
• Component/s: data structures

Environment

a ignite cluster with 2 nodes

• External issue URL: https://stackoverflow.com/questions/46343833/unexpected-behavior-of-igniteset-in-official-example
• Assignee: Evgeny Stanilovsky
• Reporter: DL Ren
• Created: 22/Sep/17 01:28
• Updated: 04/Jul/18 10:03

Description

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:

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());

Collocated set seems to work as expected. Populating from one node also doesn't create duplicates.

Issue Links

• relates to: IGNITE-7823 Separate cache for non collocated IgniteSet.