You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Andrew Mashenkov (JIRA)" <ji...@apache.org> on 2018/12/11 14:42:00 UTC
[jira] [Commented] (IGNITE-8735) Metastorage creates its own index
partition
[ https://issues.apache.org/jira/browse/IGNITE-8735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16717276#comment-16717276 ]
Andrew Mashenkov commented on IGNITE-8735:
------------------------------------------
[~astelmak], [~ivan.glukos]
I've found a link to this ticket in comment in PageMemoryTracker.checkPages(boolean) method.
As this ticket is resolved, does it mean we can safely cleanup a code?
> Metastorage creates its own index partition
> -------------------------------------------
>
> Key: IGNITE-8735
> URL: https://issues.apache.org/jira/browse/IGNITE-8735
> Project: Ignite
> Issue Type: Bug
> Components: persistence
> Reporter: Ivan Rakov
> Assignee: Alexey Stelmak
> Priority: Major
> Fix For: 2.8
>
>
> By design, all metastorage data should be stored in single partition with index = 0. However, allocatePageNoReuse is not overriden in MetastorageTree, which causes allocation of extra pages for the tree in index partition.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)