You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Dmitriy Govorukhin (JIRA)" <ji...@apache.org> on 2019/01/23 13:44:00 UTC

[jira] [Assigned] (IGNITE-10749) Improve speed of checkpoint finalization on binary memory recovery

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

Dmitriy Govorukhin reassigned IGNITE-10749:
-------------------------------------------

    Assignee: Dmitriy Govorukhin

> Improve speed of checkpoint finalization on binary memory recovery
> ------------------------------------------------------------------
>
>                 Key: IGNITE-10749
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10749
>             Project: Ignite
>          Issue Type: Improvement
>          Components: cache
>    Affects Versions: 2.0
>            Reporter: Pavel Kovalenko
>            Assignee: Dmitriy Govorukhin
>            Priority: Major
>             Fix For: 2.8
>
>
> Stopping node during checkpoint leads to binary memory recovery after node start.
> When binary memory is restored node performs checkpoint that fixes the consistent state of the page memory.
> It happens there
> {noformat}
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager#finalizeCheckpointOnRecovery
> {noformat}
> Looking at the implementation of this method we can notice that it performs finalization in 1 thread, which is not optimal. This process can be speed-up using parallelization of collecting checkpoint pages like in regular checkpoints.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)