[
https://issues.apache.org/jira/browse/IGNITE-13190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17241764#comment-17241764
]
Maxim Muzafarov commented on IGNITE-13190:
------------------------------------------
[~ibessonov]
Yes, that's why I think having dedicated DeframentationManager is not a good
thing for the code complexity in general (GridCacheDatabaseSharedManager is
shared by default and can be accessed from all the points).
There are still few minor issues left but I think we can proceed with merge.
The PR looks good to me.
Thank you also for removing TimeTracker, will you file a new issue for adding
such debug things instead? (I think [Cluster performance profiling
tool|https://cwiki.apache.org/confluence/display/IGNITE/Cluster+performance+profiling+tool]
is a good tool to do so)
> 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)
