You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Anton Kalashnikov (Jira)" <ji...@apache.org> on 2020/06/19 13:29:00 UTC

[jira] [Updated] (IGNITE-13151) Checkpointer code refactoring: extract

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

Anton Kalashnikov updated IGNITE-13151:
---------------------------------------
    Summary: Checkpointer code refactoring: extract  (was: Checkpointer code refactoring)

> Checkpointer code refactoring: extract
> --------------------------------------
>
>                 Key: IGNITE-13151
>                 URL: https://issues.apache.org/jira/browse/IGNITE-13151
>             Project: Ignite
>          Issue Type: Sub-task
>          Components: persistence
>            Reporter: Sergey Chugunov
>            Assignee: Anton Kalashnikov
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Checkpointer is at the center of Ignite persistence subsystem and more people from the community understand it the better means it is more stable and more efficient.
> However for now checkpointer code sits inside of GridCacheDatabaseSharedManager class and is entangled with this higher-level and more general component.
> To take a step forward to more modular checkpointer we need to do two things:
>  # Move checkpointer code outside database manager to a separate class.
>  # Create a well-defined API of checkpointer that will allow us to create new implementations of checkpointer in the future. An example of this is new checkpointer implementation needed for defragmentation feature purposes.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)