You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vyacheslav Koptilin (Jira)" <ji...@apache.org> on 2022/06/07 12:59:00 UTC

[jira] [Updated] (IGNITE-16010) setBaseline method must write new baseline to metastore

     [ https://issues.apache.org/jira/browse/IGNITE-16010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vyacheslav Koptilin updated IGNITE-16010:
-----------------------------------------
    Fix Version/s: 3.0.0-alpha5

> setBaseline method must write new baseline to metastore
> -------------------------------------------------------
>
>                 Key: IGNITE-16010
>                 URL: https://issues.apache.org/jira/browse/IGNITE-16010
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Kirill Gusakov
>            Assignee: Mirza Aliev
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-alpha5
>
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> Current org.apache.ignite.Ignite#setBaseline method updates assignments directly and does not save baseline as a separate source of truth anywhere.
> Instead, it should store new baseline configuration to metastore (in future it can be baseline per table). This metastore key update will be a trigger for listeners to update appropriate assignments.
> This approach provides the generalized way of baseline changing and further processing of this event by rebalancing the algorithm, for example.
> UPD: 
> It was decided to move baseline to the cluster conguration 
>  
> (Phase1)



--
This message was sent by Atlassian Jira
(v8.20.7#820007)