[GitHub] ignite pull request: Correct cluster misses aggregation

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[GitHub] ignite pull request: Correct cluster misses aggregation

andrey-kuznetsov
GitHub user krnlMustard opened a pull request:

    https://github.com/apache/ignite/pull/686

    Correct cluster misses aggregation

    When merging metrics from a cluster, node hits instead of node misses were being aggregated into merged misses.  Thus for clusters the CacheMetrics were reporting the same value for both hits and misses.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/krnlMustard/ignite patch-1

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/686.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 #686
   
----
commit ac8ae6ff0d05b99b9e352f56aac29b33af6e5c47
Author: krnlMustard <[hidden email]>
Date:   2016-05-04T16:52:47Z

    Correct cluster misses aggregation
   
    When merging metrics from a cluster, node hits instead of node misses were being aggregated into merged misses.  Thus for clusters the CacheMetrics were reporting the same value for both hits and misses.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [hidden email] or file a JIRA ticket
with INFRA.
---
Reply | Threaded
Open this post in threaded view
|

[GitHub] ignite pull request: Correct cluster misses aggregation

andrey-kuznetsov
Github user krnlMustard closed the pull request at:

    https://github.com/apache/ignite/pull/686


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [hidden email] or file a JIRA ticket
with INFRA.
---