You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexei Scherbakov (JIRA)" <ji...@apache.org> on 2019/04/23 12:02:00 UTC
[jira] [Updated] (IGNITE-11790) Optimize rebalance history
calculation.
[ https://issues.apache.org/jira/browse/IGNITE-11790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexei Scherbakov updated IGNITE-11790:
---------------------------------------
Description:
Currently we pass initial update counters to coordinator during PME.
But this is not needed for calculation rebalance history.
It can be calculated like: maxCntr - updateCounter(last counter for sequential history)
Moreother this leads to excessive rebalance volume
was:
Currently we pass initial update counters to coordinator during PME.
But this is not needed for calculation rebalance history.
It can be calculated like: maxCntr - updateCounter(last counter for sequential history)
> Optimize rebalance history calculation.
> ---------------------------------------
>
> Key: IGNITE-11790
> URL: https://issues.apache.org/jira/browse/IGNITE-11790
> Project: Ignite
> Issue Type: Improvement
> Reporter: Alexei Scherbakov
> Priority: Major
>
> Currently we pass initial update counters to coordinator during PME.
> But this is not needed for calculation rebalance history.
> It can be calculated like: maxCntr - updateCounter(last counter for sequential history)
> Moreother this leads to excessive rebalance volume
>
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)