[jira] [Commented] (HIVE-25978) Attributes not removed from org.apache.hadoop.hive.common.metrics.MetricsMBeanImpl

["Viktor Csomor (Jira)" <ji...@apache.org>]

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

Viktor Csomor commented on HIVE-25978:
--------------------------------------

After investigating this issue is has been confirmed the {{MetricMBeanImpl}} works correctly. No fix is neccessary.

{code:java}
  @Test
  public void testMBeanImpl() throws Exception {
    MBeanServer mbs = ManagementFactory.getPlatformMBeanServer();

    MetricsMBeanImpl b = new MetricsMBeanImpl();
    mbs.registerMBean(b, new ObjectName("metrics:type=test,name=test-obj"));

    b.updateAll(ImmutableMap.of("key-1", 1000, "key-2", 2000));
    b.updateAll(ImmutableMap.of("key-3", 3000, "key-4", 4000));
  }
{code}

> Attributes not removed from org.apache.hadoop.hive.common.metrics.MetricsMBeanImpl 
> -----------------------------------------------------------------------------------
>
>                 Key: HIVE-25978
>                 URL: https://issues.apache.org/jira/browse/HIVE-25978
>             Project: Hive
>          Issue Type: Bug
>          Components: Standalone Metastore
>    Affects Versions: 4.0.0
>            Reporter: Viktor Csomor
>            Assignee: Viktor Csomor
>            Priority: Minor
>              Labels: pull-request-available
>
> Investigate why the jConsole is reporting already removed attribtutes of a {{MetricsMBeanImpl}} after the {{MetricsMBeanImpl#updateAll}} has been called!
> Is there a constantly growing memory footprint of the Attributes or just some caching mechanism.
> Observed during the implementation of HIVE-25973.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)