[
https://issues.apache.org/jira/browse/IGNITE-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15008453#comment-15008453
]
ASF GitHub Bot commented on IGNITE-1932:
----------------------------------------
GitHub user akuznetsov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/242
IGNITE-1932 Fixed wrong value of BusyTimePercentage metric after
ignite.cluster().resetMetrics()
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/akuznetsov-gridgain/ignite ignite-1932
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/242.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #242
----
commit 5a116cb264a8834840fde8e5e8a60d06023d6b1a
Author: ashutak <[email protected]>
Date: 2015-11-13T13:23:56Z
Improve IgnitePutGetTxBenchmark
commit 80147128a3b07f927dec65f0a6934f6782efab5c
Author: sboikov <[email protected]>
Date: 2015-11-17T06:48:58Z
ignite-1758 Discovery fixes
commit d54fcbedf9fdc110de8e73387a6796852b0ff42c
Author: Denis Magda <[email protected]>
Date: 2015-11-17T08:56:01Z
Added advanced tests for GridCacheLoadOnlyStoreAdapterSelfTest
commit 23807374f3c43b31d474728fdcd1830308521a6c
Author: AKuznetsov <[email protected]>
Date: 2015-11-17T10:32:53Z
IGNITE-1932 Fixed busy time calculations after
ignite.cluster().resetMetrics().
----
> 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
> Assignee: 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)
