You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ignite TC Bot (JIRA)" <ji...@apache.org> on 2019/01/29 06:47:00 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16754655#comment-16754655 ]
Ignite TC Bot commented on IGNITE-10749:
----------------------------------------
{panel:title=--> Run :: All: No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=2936720&buildTypeId=IgniteTests24Java8_RunAll]
> 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
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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)