Hi, I think it is not a priority issue, because in general it is right. EVT_CACHE_REBALANCE_STOPPED event is received when all data loaded to a node, but switch of affinity happens after all cache will be rebalanced. At first, why do you need to know, when affinity change after rebalance? In my point of view, rebalance is a process which not influence on user load. Another point, you can wait all caches that are rebalancing and be sure all data was transferred.
In log you can see messages: Rebalancing scheduled [order=[ignite-sys-cache, ON_HEAP_CACHE], top=AffinityTopologyVersion [topVer=2, minorTopVer=0], rebalanceId=1, evt=NODE_JOINED, node=8138d15d-1606-4eb1-8359-d5637d500002] This means: ignite-sys-cache will rebalance first and ON_HEAP_CACHE after. After all future completed Completed rebalance future: RebalanceFuture [grp=CacheGroupContext [grp=ignite-sys-cache] ... Here a code receive a message about rebalance stopped on ignite-sys-cache. Completed rebalance future: RebalanceFuture [grp=CacheGroupContext [grp=ON_HEAP_CACHE] ... Here rebalance stopped on ON_HEAP_CACHE. You will see a topology switch on minor version Started exchange init [topVer=AffinityTopologyVersion [topVer=2, minorTopVer=1] ... Completed partition exchange [localNode=8138d15d-1606-4eb1-8359-d5637d500002, exchange=GridDhtPartitionsExchangeFuture [topVer=AffinityTopologyVersion [topVer=2, minorTopVer=1]... And only after this exchange completed you can see a new primary partition in joined node. It is what happens now. I really don’t know how to change this behavior that it will more convenient to user. If you still have use case where needs to know exactly moment of switching affinity, could you move this discussion to developer list? I hope developers can help us. On 2020/07/08 21:21:37, Humphrey <[email protected]> wrote: > Rebouncing this topic, the ticket is still open (almost 4 years). > Any progress / priority to this ticket or work around? > https://issues.apache.org/jira/browse/IGNITE-3362. > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
