You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "David Bowen (JIRA)" <ji...@apache.org> on 2007/05/22 04:18:16 UTC

[jira] Updated: (HADOOP-1406) Metrics based on Map-Reduce Counters are not cleaned up

     [ https://issues.apache.org/jira/browse/HADOOP-1406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Bowen updated HADOOP-1406:
--------------------------------

    Attachment: 1406.patch


This patch contains the API changes described above, and code which uses the modified API to clean up the counter metric data after a job is completed.

Also, it adds an extra "jobId" tag to the counter metric data, so as to avoid problems that would arise in the case where a user has two jobs with the same name running at the same time (on the same jobtracker).





> Metrics based on Map-Reduce Counters are not cleaned up
> -------------------------------------------------------
>
>                 Key: HADOOP-1406
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1406
>             Project: Hadoop
>          Issue Type: Bug
>            Reporter: David Bowen
>         Assigned To: David Bowen
>         Attachments: 1406.patch
>
>
> When map-reduce jobs are finished, the metrics corresponding to their counters are not cleaned up.  This is a memory leak, but worse it means that an ever-increasing amount of metric data is sent to the metrics system (if one is enabled).
> The fix is for JobInProgress to clean up the metrics it created when the job is complete.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.