[
https://issues.apache.org/jira/browse/OAK-7337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella closed OAK-7337.
---------------------------------
Bulk close 1.9.0
> CommitsTracker data is always empty when exposed via JMX
> --------------------------------------------------------
>
> Key: OAK-7337
> URL: https://issues.apache.org/jira/browse/OAK-7337
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar
> Reporter: Andrei Dulceanu
> Assignee: Andrei Dulceanu
> Priority: Major
> Labels: tooling
> Fix For: 1.9.0, 1.10
>
>
> Due to duplicate registration of {{SegmentNodeStoreStats}} in both
> {{SegmentNodeStore}} and {{LockBasedScheduler}}, we end up with two
> instances of this MBean. The former gets exposed via JMX and always returns
> empty tables for CommitsCountPerWriter and QueuedWriters, while the latter
> correctly tracks these data, but is not exposed. To address this, we should
> stick to only one instance of {{SegmentNodeStoreStats}}, used in both
> {{SegmentNodeStore}} and {{LockBasedScheduler}}.
> While at this, two additional points to be addressed:
> # {{CommitsTracker}} needs to be unit tested
> # commits count map size needs to be configurable via
> {{SegmentNodeStoreStats}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
