You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Aleksey Plekhanov (Jira)" <ji...@apache.org> on 2020/07/03 06:27:00 UTC
[jira] [Updated] (IGNITE-10409) ExchangeFuture should be in charge
on cancelling rebalancing process
[ https://issues.apache.org/jira/browse/IGNITE-10409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aleksey Plekhanov updated IGNITE-10409:
---------------------------------------
Fix Version/s: (was: 2.9)
> ExchangeFuture should be in charge on cancelling rebalancing process
> --------------------------------------------------------------------
>
> Key: IGNITE-10409
> URL: https://issues.apache.org/jira/browse/IGNITE-10409
> Project: Ignite
> Issue Type: Improvement
> Components: general
> Reporter: Sergey Chugunov
> Priority: Major
>
> Ticket IGNITE-7165 introduced improvement of not cancelling any on-going partition rebalancing process when client node joins topology. Client join event doesn't change affinity distribution so on-going rebalance remains valid, no need to cancel it and restart again.
> Implementation was based on introducing new method *rebalanceRequired* in *GridCachePreloader* interface.
> At the same time PME optimizations efforts enhanced ExchangeFuture functionality so now the future itself contains all information about weather affinity changed or not.
> We need to rework code changes from IGNITE-7165 and base it on ExchangeFuture functionality instead of new method in Preloader interface.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)