[
https://issues.apache.org/jira/browse/IGNITE-20741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy updated IGNITE-20741:
---------------------------------------
Description:
Each revision has its own timestamp. When notifying a watch, we must send the
timestamp {_}corresponding to the revision{_}.
When recovering MetaStorage, we may find that some revision range was not yet
processed by watches, so we notify watches for these revisions.
The problem is that, when we do this, we send the same timestamp (the one
corresponding to the lowest revision under recovery) for every revision.
> Incorrect timestamps may be used when notifying watches on MetaStorage
> recovery
> -------------------------------------------------------------------------------
>
> Key: IGNITE-20741
> URL: https://issues.apache.org/jira/browse/IGNITE-20741
> Project: Ignite
> Issue Type: Bug
> Reporter: Roman Puchkovskiy
> Assignee: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> Each revision has its own timestamp. When notifying a watch, we must send the
> timestamp {_}corresponding to the revision{_}.
> When recovering MetaStorage, we may find that some revision range was not yet
> processed by watches, so we notify watches for these revisions.
> The problem is that, when we do this, we send the same timestamp (the one
> corresponding to the lowest revision under recovery) for every revision.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
