You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladislav Pyatkov (Jira)" <ji...@apache.org> on 2024/07/25 18:24:00 UTC

[jira] [Updated] (IGNITE-22843) Writing into RAFT log is too long

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

Vladislav Pyatkov updated IGNITE-22843:
---------------------------------------
    Summary: Writing into RAFT log is too long  (was: Writing into ARFT log is too long)

> Writing into RAFT log is too long
> ---------------------------------
>
>                 Key: IGNITE-22843
>                 URL: https://issues.apache.org/jira/browse/IGNITE-22843
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Vladislav Pyatkov
>            Priority: Major
>              Labels: ignite-3
>
> h3. Motivation
> We are using RocksDB as RAFT log storage. Writing in the log is significantly longer than writing in the memory-mapped buffer (as we used in Ignite 2).
> {noformat}
> appendLogEntry 0.8 6493700 6494500
> Here is hidden 0.5 us
> flushLog 20.1 6495000 6515100
> Here is hidden 2.8 us
> {noformat}
> h3. Definition of done
> We should find a way to implement faster log storage.



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