You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by "Sergey Kozlov (JIRA)" <ji...@apache.org> on 2015/09/23 21:53:04 UTC

[jira] [Created] (IGNITE-1535) Evicted entries still are presented

Sergey Kozlov created IGNITE-1535:
-------------------------------------

             Summary: Evicted entries still are presented 
                 Key: IGNITE-1535
                 URL: https://issues.apache.org/jira/browse/IGNITE-1535
             Project: Ignite
          Issue Type: Bug
          Components: cache
    Affects Versions: ignite-1.4
            Reporter: Sergey Kozlov
            Assignee: Yakov Zhdanov
             Fix For: ignite-1.5


Test creates 4 caches: 2 PARTITIONED for testing and 2 REPLICATED for comparison. Each cache has FIFO eviction policy with maxSize=750.
Test puts 1000 entries (order: 1 ... 1000) and check that 1..250 entries are removed and 251..1000 presented in cache.

1. Copy grid_evict.xml in examples/config directory
2. Copy CacheFifoEvictExample in examples/src/main/java/org/apache/ignite/examples/datagrid
3. Build examples
4. Run 3 nodes bin/ignite.sh examples/config/grid_evict.xml
5. Run CacheFifoEvictExample

Expected output:
{noformat}
>>>cache_1
put keys 1..1000
get keys 1..1000
>>>cache_2
put keys 1..1000
get keys 1..1000
{noformat}

Bur for PARTITIONED caches I got
{noformat}
>>>cache_1
put keys 1..1000
get keys 1..1000
>>> not null value found for 18
>>> not null value found for 19
>>> not null value found for 20
>>> not null value found for 21
>>> not null value found for 22
>>> not null value found for 23
>>> not null value found for 24
>>> not null value found for 25
>>> not null value found for 28
...
>>>cache_2
put keys 1..1000
get keys 1..1000
>>> not null value found for 1
>>> not null value found for 3
>>> not null value found for 6
>>> not null value found for 10
>>> not null value found for 18
>>> not null value found for 19
>>> not null value found for 20
>>> not null value found for 21
>>> not null value found for 22
>>> not null value found for 23
>>> not null value found for 24
>>> not null value found for 25
...
{noformat}


Delay between puts and gets doesn't fix the issue but add null values for keys > 250



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)