[jira] [Updated] (IGNITE-8735) Metastorage creates its own index partition

2018-08-29 Thread Ivan Rakov (JIRA)


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

Ivan Rakov updated IGNITE-8735:
---
Fix Version/s: (was: 2.7)
   2.8

> 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
>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)


[jira] [Updated] (IGNITE-8735) Metastorage creates its own index partition

2018-06-26 Thread Dmitriy Pavlov (JIRA)


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

Dmitriy Pavlov updated IGNITE-8735:
---
Fix Version/s: (was: 2.6)
   2.7

> 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
>Priority: Major
> Fix For: 2.7
>
>
> 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)


[jira] [Updated] (IGNITE-8735) Metastorage creates its own index partition

2018-06-07 Thread Ivan Rakov (JIRA)


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

Ivan Rakov updated IGNITE-8735:
---
Description: 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.  (was: By design, all metastorage data should be stored in single 
partition with index = 0. However, allocatePageNoReuse is not overriden in 
MetastorageTree, which cause allocation of extra pages for the tree in index 
partition.)

> 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
>Priority: Major
> Fix For: 2.6
>
>
> 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)