[
https://issues.apache.org/jira/browse/IGNITE-15910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Lapin updated IGNITE-15910:
-------------------------------------
Description:
h3. Context
General concept of processing distributed notifications from meta storage
assumes that such events will be processed synchronously one after another with
sort of finalization step during which watch event projection is committed to
vault together with corresponding applied revision. It's worth to mention that
it's guaranteed that all notification events with same revision will be grouped
to one and only one watch event.
Besides synchronous watch events processing it's guaranteed that
MetaStorageManager also notifies components about related distributed updates
synchronously in the components hierarchy order. In other words, within meta
storage watch notification processing thread, MetaStorageManager funs-out
corresponding sub-notifications to component A, then, when component A
finishes it's notification processing, to component B, then, when B finishes
it's part, to C, etc.
So far so good. Components cannot overtake each other in knowledge of the
distribution state. Also if node stops of fails it's guaranteed, that after
restart, it'll continue to retrieve the notifications from the last seen
applied revision .
Problem
> Pending actions are lost in case of node stop
> ---------------------------------------------
>
> Key: IGNITE-15910
> URL: https://issues.apache.org/jira/browse/IGNITE-15910
> Project: Ignite
> Issue Type: Bug
> Reporter: Alexander Lapin
> Priority: Major
> Labels: ignite-3
>
> h3. Context
> General concept of processing distributed notifications from meta storage
> assumes that such events will be processed synchronously one after another
> with sort of finalization step during which watch event projection is
> committed to vault together with corresponding applied revision. It's worth
> to mention that it's guaranteed that all notification events with same
> revision will be grouped to one and only one watch event.
> Besides synchronous watch events processing it's guaranteed that
> MetaStorageManager also notifies components about related distributed
> updates synchronously in the components hierarchy order. In other words,
> within meta storage watch notification processing thread, MetaStorageManager
> funs-out corresponding sub-notifications to component A, then, when
> component A finishes it's notification processing, to component B, then, when
> B finishes it's part, to C, etc.
> So far so good. Components cannot overtake each other in knowledge of the
> distribution state. Also if node stops of fails it's guaranteed, that after
> restart, it'll continue to retrieve the notifications from the last seen
> applied revision .
> Problem
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
