You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Sergey Kosarev (JIRA)" <ji...@apache.org> on 2018/09/12 16:15:00 UTC
[jira] [Commented] (IGNITE-9309) LocalNodeMovingPartitionsCount
metrics may calculates incorrect due to processFullPartitionUpdate
[ https://issues.apache.org/jira/browse/IGNITE-9309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16612411#comment-16612411 ]
Sergey Kosarev commented on IGNITE-9309:
----------------------------------------
[~Mmuzaf], is there any progress/estimate?
> LocalNodeMovingPartitionsCount metrics may calculates incorrect due to processFullPartitionUpdate
> -------------------------------------------------------------------------------------------------
>
> Key: IGNITE-9309
> URL: https://issues.apache.org/jira/browse/IGNITE-9309
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.6
> Reporter: Maxim Muzafarov
> Assignee: Oleg Ostanin
> Priority: Major
> Attachments: GridCacheRebalancingCancelTestNoReproduce.java, node-2-jstack.log, node-NO_REBALANCE-7165.log
>
>
> [~qvad] have found incorrect {{LocalNodeMovingPartitionsCount}} metrics calculation on client node {{JOIN\LEFT}}. Full issue reproducer is absent.
> Probable scenario:
> {code}
> Repeat 10 times:
> 1. stop node
> 2. clean lfs
> 3. add stopped node (trigger rebalance)
> 4. 3 times: start 2 clients, wait for topology snapshot, close clients
> 5. for each cache group check JMX metrics LocalNodeMovingPartitionsCount (like waitForFinishRebalance())
> {code}
> Whole discussion and all configuration details can be found in comments of [IGNITE-7165|https://issues.apache.org/jira/browse/IGNITE-7165].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)