[
https://issues.apache.org/jira/browse/IGNITE-6483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16189596#comment-16189596
]
Ilya Kasnacheev commented on IGNITE-6483:
-----------------------------------------
It turns out statistics should be enabled for relevant cache and hardbeat
should be waited for.
This makes MX beans unusable for anything other than steady-state monitoring. I
will create tests for that behavior.
> Entries count in caches' MX Beans not immediately available
> -----------------------------------------------------------
>
> Key: IGNITE-6483
> URL: https://issues.apache.org/jira/browse/IGNITE-6483
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.1
> Reporter: Ilya Kasnacheev
> Assignee: Ilya Kasnacheev
> Attachments: IgniteCacheMxBeansTest.java
>
>
> When querying properties like
> {code}
> cache.mxBean().getOffHeapPrimaryEntriesCount()
> {code}
> The value is often 0 (zero) initially, even if cache is not empty and located
> in offheap.
> Local MX Bean returns correct value.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)