[
https://issues.apache.org/jira/browse/IGNITE-20290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17759842#comment-17759842
]
Roman Puchkovskiy commented on IGNITE-20290:
--------------------------------------------
IGNITE-20300 was split out to fix it separately
> Command reordering wrt safe time in MetaStorage
> -----------------------------------------------
>
> Key: IGNITE-20290
> URL: https://issues.apache.org/jira/browse/IGNITE-20290
> Project: Ignite
> Issue Type: Bug
> Reporter: Roman Puchkovskiy
> Assignee: Roman Puchkovskiy
> Priority: Blocker
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> # No mechanism exists to forbid reordering of idle safe time propagation
> commands wrt other MetaStorage write commands
> # The mechanism that forbids mutual reordering of normal MetaStorage write
> commands lacks synchronization
> # Idle safe time propagation commands update the safe time tracker too early
> (on command application; instead if should be done on revision application in
> watches)
> To solve item 1, we could reuse the mechanism mentioned in item 2.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
