[
https://issues.apache.org/jira/browse/IGNITE-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15055664#comment-15055664
]
ASF GitHub Bot commented on IGNITE-1932:
----------------------------------------
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/242
> Wrong value of BusyTimePercentage metric after ignite.cluster().resetMetrics()
> ------------------------------------------------------------------------------
>
> Key: IGNITE-1932
> URL: https://issues.apache.org/jira/browse/IGNITE-1932
> Project: Ignite
> Issue Type: Bug
> Components: compute
> Affects Versions: ignite-1.4
> Reporter: Alexey Kuznetsov
> Fix For: 1.5
>
>
> I found that after call of
> ignite.cluster().resetMetrics()
> BusyTimePercentage became 100%
> After some debug I found that BusyTimePercentage - calculated as:
> 1 - IdleTimePercentage
> and IdleTimePercentage calculated as IdleTime / UpTime
> and on reset we set IdleTime to 0.
> So the possible fix is to preserve IdleTime on reset.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
