You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Maxim Muzafarov (Jira)" <ji...@apache.org> on 2020/02/13 11:20:00 UTC
[jira] [Updated] (IGNITE-8571) Baseline auto-adjust feature
[ https://issues.apache.org/jira/browse/IGNITE-8571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maxim Muzafarov updated IGNITE-8571:
------------------------------------
Labels: IEP-4 Phase-2 important (was: IEP-4 Phase-2)
> Baseline auto-adjust feature
> ----------------------------
>
> Key: IGNITE-8571
> URL: https://issues.apache.org/jira/browse/IGNITE-8571
> Project: Ignite
> Issue Type: New Feature
> Reporter: Eduard Shangareev
> Assignee: Anton Kalashnikov
> Priority: Major
> Labels: IEP-4, Phase-2, important
> Fix For: 2.8
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Now we have only one way to change BLAT - manually update it via console.sh or API.
> We need to add the possibility to change it automatically. Adjust to current topology.
> So, I propose 2 new distributed parameters which would be responsible to tune this feature.
> 1. Flag autoAdjustEnabled - true/false. Easy. Manual baseline control or auto adjusting baseline.
> 2. autoAdjustTimeout - time which we would wait after the actual topology change. But it would be reset if new discovery event happened. (node join/exit).
> We need to change API next way:
> org.apache.ignite.IgniteCluster:
> * isBaselineAutoAdjustEnabled()
> * setBaselineAutoAdjustEnabled(boolean enabled);
> * setBaselineAutoAdjustTimeout(long timeoutInMs);
> Also, we need to ensure that all nodes would have the same parameters(distributed parameters).
> And we should be able to survive coordinator left during parameters changes.
> When autoAdjustEnabled is true we should be block ability to manual baseline change.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)