You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Maxim Muzafarov (Jira)" <ji...@apache.org> on 2019/10/10 12:41:00 UTC
[jira] [Updated] (IGNITE-10508) Need to support the new checkpoint
feature, checkpint should not wait for the previous operation to complete
[ https://issues.apache.org/jira/browse/IGNITE-10508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maxim Muzafarov updated IGNITE-10508:
-------------------------------------
Fix Version/s: (was: 2.8)
2.9
> Need to support the new checkpoint feature, checkpint should not wait for the previous operation to complete
> ------------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-10508
> URL: https://issues.apache.org/jira/browse/IGNITE-10508
> Project: Ignite
> Issue Type: New Feature
> Reporter: Dmitriy Govorukhin
> Assignee: Dmitriy Govorukhin
> Priority: Critical
> Fix For: 2.9
>
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> There are cases we should trigger the checkpoint, some operations will be sure that all operation finished before the checkpoint. It is necessary to support the possibility of run checkpoint without waiting for the completion of the previous checkpoint.
> Solution:
> Merge checkpoint pages and append write new dirty pages to a current checkpoint.
> Restrictions:
> Trigger new checkpoint should not wait for the previous checkpoint operation completed.
> - It should not break crash recovery mechanisms
> - Only one merged is allow in the first implementation (potentially OOM, if we will try to merge many checkpoint operations)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)