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

Kirill Tkalenko updated IGNITE-20866:
-------------------------------------
    Fix Version/s: 3.0.0-beta2

> Race condition in configuration initialization using meta storage revision
> --------------------------------------------------------------------------
>
>                 Key: IGNITE-20866
>                 URL: https://issues.apache.org/jira/browse/IGNITE-20866
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Ivan Gagarkin
>            Assignee: Ivan Gagarkin
>            Priority: Critical
>              Labels: ignite-3
>             Fix For: 3.0.0-beta2
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> {*}Summary{*}{_}:{_} Initialization of the cluster configuration using meta 
> storage revision 0 leads to race conditions, resulting in potential 
> misconfiguration.
> {*}Analysis{*}: Currently, the system applies the initial cluster 
> configuration locally when the meta-storage revision is at 0. This approach 
> can lead to race conditions where the initial configuration might be 
> overlooked if the revision number changes during the initialization process.
> _Suggested Fix:_ We should modify the initialization logic to:
>  # Use the local revision of the configuration key.
>  # If the local revision is absent, only then fall back to the initial 
> configuration.
> This approach would prevent the configuration from being ignored due to 
> changes in the meta-store revision.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to