[
https://issues.apache.org/jira/browse/IGNITE-6903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16290481#comment-16290481
]
Vladimir Ozerov commented on IGNITE-6903:
-----------------------------------------
[~avinogradov], [~alex_pl], [~NIzhikov], [~dmagda],
Folks, what is the rationale behind this new metric? The very problem is that
it is located in the wrong place. Indexes do not belong to data region. They
belong to *tables*, which in turn belong to caches, which belong to cache
groups, which in turn belong to data region. And the fact that you can easily
count number of allocated pages for all indexes is merely implementation detail
- currently we store all indexes of particular cache group in a single file
"index.bin". But this is not carved in stone, and most likely to be changed in
future in favor of traditional "tablespace - segment - extent" approach for the
sake of scan performance.
Who and how would use this metric?
> Implement new JMX metrics for Indexing
> --------------------------------------
>
> Key: IGNITE-6903
> URL: https://issues.apache.org/jira/browse/IGNITE-6903
> Project: Ignite
> Issue Type: New Feature
> Reporter: Anton Vinogradov
> Assignee: Nikolay Izhikov
> Priority: Critical
> Labels: iep-6, important
> Fix For: 2.4
>
>
> These additional metrics and methods should be implemented:
> - Space occupied by indexes.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
