It seems to me that EVT_CACHE_REBALANCE_OBJECT_LOADED events are coming on the backup node of their entries, and never on primary node as it should in according to the doco.

I have a partitioned cache, with 1 backup copy configured.

After a cluster node is killed (out of say 3 or 4 running initially), a rebalance happens, and I observe EVT_CACHE_REBALANCE_OBJECT_LOADED events using ignite.events().localListen(...). If I check where this event.key() maps to by calling affinity.mapKeyToNode(key), I get a node for which isLocal() is false.

I also check mapKeyToPrimaryAndBackups(key), and indeed, the second node in the returned collection says that its isLocal() is true.

I also double check it by re-querying local entries on each node by local ScanQuery(), and it confirms the above, i.e. whatever I received with EVT_CACHE_REBALANCE_OBJECT_LOADED, has primary node which is different from where I receive it.

I.e. the EVT_CACHE_REBALANCE_OBJECT_LOADED event never comes on primary node of the event’s object, but always on the backup node.

So… is it correct at all?

Thanks, I would appreciate help on that – spent quite some time so far on that, any clue would matter!!