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

Mirza Aliev updated IGNITE-16010:
---------------------------------
    Description: 
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)

  was:
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 cluster conguration 

 

(Phase1)


> 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
>          Time Spent: 10m
>  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.1#820001)

Reply via email to