ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Mashenkov (JIRA)" <j...@apache.org>
Subject [jira] [Created] (IGNITE-7832) Partition lost events looks broken.
Date Tue, 27 Feb 2018 15:21:00 GMT
Andrew Mashenkov created IGNITE-7832:

             Summary: Partition lost events looks broken.
                 Key: IGNITE-7832
                 URL: https://issues.apache.org/jira/browse/IGNITE-7832
             Project: Ignite
          Issue Type: Task
          Components: cache
            Reporter: Andrew Mashenkov
             Fix For: 2.5

Steps to reproduce:
 # Start 3 nodes with Partitioned cache with no backups.
 Register event handlers for EVT_CACHE_REBALANCE_PART_DATA_LOST event. 
PartitionLossPolicy should be smth other then IGNORED (which is default).
 # Put some data and make sure rebalance is finished.
 # Kill first node. 
I observer partition lost events on 2-nd node only however, some of them should be owned
by 3-rd node according new topology. 
Cache.lostPartitions() returns non-empty resultset on 2-nd node only.
 # Kill 2-nd node. 
No partition lost events will be fired on 3-rd node. However data is obviously lost.
Cache.lostPartitions() returns empty resultset.

Looks like partition lost events mechanics is broken and should be fixed.

This message was sent by Atlassian JIRA

View raw message