Re: Primary partitions return zero partitions before rebalance.

2019-04-04 Thread Павлухин Иван
Ah, sorry for that. PME = Partition Map Exchange. It is described along with late affinity assignment in article you referenced earlier [1]. [1] https://cwiki.apache.org/confluence/display/IGNITE/%28Partition+Map%29+Exchange+-+under+the+hood#id-(PartitionMap)Exchange-under вт, 2 апр. 2019 г. в

Re: Primary partitions return zero partitions before rebalance.

2019-04-02 Thread Koitoer
Sorry but what is exactly the PME ? On Mon, Apr 1, 2019 at 1:55 AM Павлухин Иван wrote: > Hi, > > Sorry for the late answer. An observed result seems expected to me. I > suppose following: > 1. EVT_CACHE_REBALANCE_STOPPED is fired when a particular node loaded > all partitions which it will be

Re: Primary partitions return zero partitions before rebalance.

2019-04-01 Thread Павлухин Иван
Hi, Sorry for the late answer. An observed result seems expected to me. I suppose following: 1. EVT_CACHE_REBALANCE_STOPPED is fired when a particular node loaded all partitions which it will be responsible for. 2. All nodes it the cluster must become aware that partition assignment was changed.

Re: Primary partitions return zero partitions before rebalance.

2019-03-19 Thread Koitoer
Hello Igniters The version of Ignite that we are using is 2.7.0. I'm adding the events that I want to hear via the IgniteConfiguration using the `setIncludeEventTypes` Then using ignite.event().localListen(listenerPredicate, eventTypes); EVT_CACHE_REBALANCE_STARTED, EVT_CACHE_REBALANCE_STOPPED,

Re: Primary partitions return zero partitions before rebalance.

2019-03-15 Thread Павлухин Иван
Hi, What Ignite version do you use? How do you register your listener? On what object do you call primaryPartitions/allPartitions? It is true that Ignite uses late affinitly assignment. And it means that for each topology change (node enter or node leave) parttion assigment changes twice. First

Primary partitions return zero partitions before rebalance.

2019-03-13 Thread Koitoer
Hi All. I'm trying to follow the rebalance events of my ignite cluster so I'm able to track which partitions are assigned to each node at any point in time. I am listening to the `EVT_CACHE_REBALANCE_STARTED` and `EVT_CACHE_REBALANCE_STOPPED` events from Ignite and that is working well, except in