Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
No link here, failure can be reproduced locally.
Here's the flow of events:
- MetaStorageManager#storeEntries starts its execution, revision is equal to 2, for example;
- At the same time, MetaStorageManager#updateAggregatedWatch is called by the inhibitor in the test;
- "storeEntries" reads an applied revision value, it's 1.
- "updateAggregatedWatch" reads an applied revision value, it's still 1.
- New watch is started, using revision 2 as a base.
- "storeEntries" writes data into the vault, applied revision becomes 2.
- New event from new watch appears:
- revision of the event is 2, because that's the base;
- revision read from Vault is also 2;
- we get an exception that these two cannot be equal.
Attachments
Issue Links
- is fixed by
-
IGNITE-18397 Rework Watches based on learners
- Resolved
- relates to
-
IGNITE-18410 Put data to metastorage during some components start leads to assertion error
- Resolved