[ 
https://issues.apache.org/jira/browse/IGNITE-2616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15304242#comment-15304242
 ] 

ASF GitHub Bot commented on IGNITE-2616:
----------------------------------------

GitHub user vldpyatkov opened a pull request:

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

    IGNITE-2616

    IGNITE-2616
    NonHeap memory usage metrics don't work as expected.

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

    $ git pull https://github.com/vldpyatkov/ignite ignite-2616

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

    https://github.com/apache/ignite/pull/762.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 #762
    
----
commit cacb62a92888cc27f9baab9a27518e66bfc3484e
Author: vdpyatkov <[email protected]>
Date:   2016-05-27T15:41:11Z

    IGNITE-2616
    NonHeap memory usage metrics don't work as expected.

----


> NonHeap memory usage metrics don't work as expected.
> ----------------------------------------------------
>
>                 Key: IGNITE-2616
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2616
>             Project: Ignite
>          Issue Type: Bug
>          Components: general
>    Affects Versions: 1.5.0.final
>            Reporter: Vladimir Ershov
>            Assignee: Vladislav Pyatkov
>            Priority: Minor
>         Attachments: ClusterMetricsOnCacheSelfTest.java
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> This simple code:
> {noformat}
>     public static void main(String ... args) {
>         MemoryMXBean mxBean = ManagementFactory.getMemoryMXBean();
>         System.out.println(mxBean.getNonHeapMemoryUsage());
>         GridUnsafeMemory uMem = new GridUnsafeMemory(1024L * 1024 * 1024 * 
> 3); //3GB
>         System.out.println(mxBean.getNonHeapMemoryUsage());
>         uMem.allocate(1024 * 1024 * 1024, true, false);
>         System.out.println(mxBean.getNonHeapMemoryUsage());
>         uMem.allocate(1024 * 1024 * 1024, true, true);
>         System.out.println(mxBean.getNonHeapMemoryUsage());
>     }
> {noformat}
> shows: 
> {noformat}
> init = 2555904(2496K) used = 4783352(4671K) committed = 8060928(7872K) max = 
> -1(-1K)
> init = 2555904(2496K) used = 5018704(4901K) committed = 8060928(7872K) max = 
> -1(-1K)
> init = 2555904(2496K) used = 5018960(4901K) committed = 8060928(7872K) max = 
> -1(-1K)
> init = 2555904(2496K) used = 5018960(4901K) committed = 8060928(7872K) max = 
> -1(-1K)
> {noformat}
> which means: offHeap metrics are incorrect. The  problem is: Apache Ignite 
> uses that MemoryMXBean  for collecting metrics, thus Apache Ignite offHeap 
> metrics are incorrect too. We should find the way to fix this, if there are 
> any.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to