You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Dmitry Sherstobitov (JIRA)" <ji...@apache.org> on 2018/01/17 15:18:00 UTC
[jira] [Commented] (IGNITE-7449) Rebalancing metrics doesn't
display actual information about current rebalance state
[ https://issues.apache.org/jira/browse/IGNITE-7449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16328872#comment-16328872 ]
Dmitry Sherstobitov commented on IGNITE-7449:
---------------------------------------------
I've investigated this problem and found that observable cache have small amount of data on the node.
So rebalance metrics have long type - observable values are less that 1 and displayed as 0.
On massive caches this metrics displays correct information.
> Rebalancing metrics doesn't display actual information about current rebalance state
> ------------------------------------------------------------------------------------
>
> Key: IGNITE-7449
> URL: https://issues.apache.org/jira/browse/IGNITE-7449
> Project: Ignite
> Issue Type: Bug
> Reporter: Dmitry Sherstobitov
> Priority: Major
>
> In case of shutdown node with clear LFS following metrics doesn't display correct information about rebalance:
> RebalancingKeysRate
> RebalancingBytesRate
> KeysToRebalanceLeft
>
> Otherwise RebalancingPartitionsCount metric displays information correctly
> Steps to reproduce:
> 1. Cluster with enabled statistics
> 2. Shutdown node and clear LFS
> 3. Run node
> 4. Start node and ask node for current rebalance state through JMX:
> Current result:
> 1 tick
> RebalancingKeysRate 0
> RebalancingBytesRate 0
> KeysToRebalanceLeft 0
> RebalancingPartitionsCount 342
> 2 tick
> RebalancingKeysRate 0
> RebalancingBytesRate 0
> KeysToRebalanceLeft 0
> RebalancingPartitionsCount 80
> Expected:
> 2 tick
> RebalancingKeysRate SOME_NON_ZERO_VALUE
> RebalancingBytesRate SOME_NON_ZERO_VALUE
> KeysToRebalanceLeft SOME_NON_ZERO_VALUE
> RebalancingPartitionsCount 80
>
> UPD: -DIGNITE_REBALANCE_STATISTICS_TIME_INTERVAL=1000 doesn't affect results
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)