[
https://issues.apache.org/jira/browse/OAK-1451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13949111#comment-13949111
]
Thomas Mueller commented on OAK-1451:
-------------------------------------
Currently, the counting only goes to about 100, and it stops then. It's not
possible to use that information. The extrapolation is for queries with
"property in (a, b, c)" (roughly: count the number of entries where property =
a, and multiply by 3). That's not related to this issue.
> Expose index size
> -----------------
>
> Key: OAK-1451
> URL: https://issues.apache.org/jira/browse/OAK-1451
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: query
> Reporter: Michael Marth
> Assignee: Alex Parvulescu
> Priority: Minor
> Labels: production, resilience
> Fix For: 0.20
>
>
> At the moment some MK's disc needs are largely from the indexes. Maybe we can
> do something about this, but in the meantime it would be helpful if we could
> expose the index sizes (num of indexed nodes) via JMX so that they could be
> easily monitored.
> This would also be helpful to see at which point an index becomes useless (if
> the majority of content nodes are indexed one might as well not have an index)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
