You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Roman Puchkovskiy (Jira)" <ji...@apache.org> on 2023/08/29 12:06:00 UTC

[jira] [Updated] (IGNITE-20300) Metastorage command reordering wrt Safe Time on Raft Group entry

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

Roman Puchkovskiy updated IGNITE-20300:
---------------------------------------
    Description: Safe time is updated on write commands just before they are added to JRaft's LogManager. But this is done in many threads and there is no enough synchronization, so it's possible that a command with a higher timestamp gets linearized before a command with a lower timestamp.  (was: TBD)

> Metastorage command reordering wrt Safe Time on Raft Group entry
> ----------------------------------------------------------------
>
>                 Key: IGNITE-20300
>                 URL: https://issues.apache.org/jira/browse/IGNITE-20300
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Roman Puchkovskiy
>            Assignee: Roman Puchkovskiy
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-beta2
>
>
> Safe time is updated on write commands just before they are added to JRaft's LogManager. But this is done in many threads and there is no enough synchronization, so it's possible that a command with a higher timestamp gets linearized before a command with a lower timestamp.



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