You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ratis.apache.org by "Tsz-wo Sze (Jira)" <ji...@apache.org> on 2024/08/09 16:15:00 UTC

[jira] [Updated] (RATIS-2136) Fixed the issue that RatisServer could not start after frequent restarts

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

Tsz-wo Sze updated RATIS-2136:
------------------------------
    Component/s: server

> Fixed the issue that RatisServer could not start after frequent restarts
> ------------------------------------------------------------------------
>
>                 Key: RATIS-2136
>                 URL: https://issues.apache.org/jira/browse/RATIS-2136
>             Project: Ratis
>          Issue Type: Bug
>          Components: server
>            Reporter: Xinyu Tan
>            Assignee: Xinyu Tan
>            Priority: Major
>         Attachments: image-2024-08-08-14-48-17-943.png, image-2024-08-08-14-48-33-657.png
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
>  !image-2024-08-08-14-48-17-943.png! 
>  !image-2024-08-08-14-48-33-657.png! 
> Currently, in the key write path of Ratis, segment switching and log persistence are asynchronous. Therefore, when Ratis shuts down triggering an automatic snapshot or when a user manually triggers a snapshot, it is possible that the snapshot has already been generated while the corresponding log has not yet been persisted. In such cases, a restart might fail. This issue needs to be fixed.



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