[jira] [Updated] (IGNITE-19129) Remove parallel Watch processing

["Aleksandr Polovtcev (Jira)" <ji...@apache.org>]

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

Aleksandr Polovtcev updated IGNITE-19129:
-----------------------------------------
    Description: 
Current implementation of Parallel Meta Storage Watches works as following:
# Every Watch has an associated unique ID and is processed independently from other Watches.
# After a Watch has finished processing an event, the processed revision and the Watch ID gets saved in the Vault.
# During recovery, a minimum processed revision is computed among all Watches and events are replayed, starting from that revision. If a Watch has already processed an event, it discards it.
 
This approach leads to a problem which can happen during recovery when interacting with the Configuration component:

WIP 

> Remove parallel Watch processing
> --------------------------------
>
>                 Key: IGNITE-19129
>                 URL: https://issues.apache.org/jira/browse/IGNITE-19129
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Aleksandr Polovtcev
>            Assignee: Aleksandr Polovtcev
>            Priority: Major
>              Labels: ignite-3
>
> Current implementation of Parallel Meta Storage Watches works as following:
> # Every Watch has an associated unique ID and is processed independently from other Watches.
> # After a Watch has finished processing an event, the processed revision and the Watch ID gets saved in the Vault.
> # During recovery, a minimum processed revision is computed among all Watches and events are replayed, starting from that revision. If a Watch has already processed an event, it discards it.
>  
> This approach leads to a problem which can happen during recovery when interacting with the Configuration component:
> WIP 



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