hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Nauroth (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-10839) Add unregisterSource() to MetricsSystem API
Date Wed, 16 Jul 2014 00:03:04 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-10839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14062898#comment-14062898

Chris Nauroth commented on HADOOP-10839:

The test failures are unrelated.  This is the same set of tests that have been failing intermittently
on the new Jenkins hosts.

> Add unregisterSource() to MetricsSystem API
> -------------------------------------------
>                 Key: HADOOP-10839
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10839
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: metrics
>    Affects Versions: 2.4.1
>            Reporter: shanyu zhao
>            Assignee: shanyu zhao
>         Attachments: HADOOP-10839.2.patch, HADOOP-10839.patch
> Currently the MetrisSystem API has register() method to register a MetricsSource but
doesn't have unregister() method. This means once a MetricsSource is registered with the MetricsSystem,
it will be there forever until the MetricsSystem is shut down. This in some cases can cause
Java OutOfMemoryError.
> One such case is in file system metrics implementation. The new AbstractFileSystem/FileContext
framework does not implement a cache so every file system access can lead to the creation
of a NativeFileSystem instance. (refer to HADOOP-6356). And all these NativeFileSystem needs
to share the same instance of MetricsSystemImpl, which means we cannot shut down MetricsSystem
to clean up all the MetricsSources that has been registered but no longer active. Over time
the MetricsSource instance accumulates and eventually we saw OutOfMemoryError.

This message was sent by Atlassian JIRA

View raw message