[
https://issues.apache.org/jira/browse/IGNITE-13190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17241511#comment-17241511
]
Ivan Bessonov commented on IGNITE-13190:
----------------------------------------
Hi, [~mmuzaf],
it's kinda hard to keep up for all the comments, but I hope that I fixed
everything that you asked. TimeTracker is removed.
Last questionable thing, I guess, is checkpoint lock as a method parameter. We
either pass it as is or somehow access it through
GridCacheDatabaseSharedManager. This would mean that we must provide a public
accessor method for "CachePartitionDefragmentationManager", which is also
strange.
Please take a look, thank you!
> Core defragmentation functions
> ------------------------------
>
> Key: IGNITE-13190
> URL: https://issues.apache.org/jira/browse/IGNITE-13190
> Project: Ignite
> Issue Type: Sub-task
> Reporter: Sergey Chugunov
> Assignee: Ivan Bessonov
> Priority: Major
> Labels: IEP-47
> Time Spent: 20h 40m
> Remaining Estimate: 0h
>
> The following set of functions covering defragmentation happy-case needed:
> * Initialization of defragmentation manager when node is started in
> maintenance mode.
> * Information about partition files is gathered by defrag mgr.
> * For each partition file corresponding file of defragmented partition is
> created and initialized.
> * Keys are transferred from old partitions to new partitions.
> * Checkpointer is aware of new partition files and flushes defragmented
> memory to new partition files.
>
> No fault-tolerance code nor index defragmentation mappings are needed in this
> task.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
