hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siddharth Seth (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-3511) Counters occupy a good part of AM heap
Date Mon, 09 Jan 2012 20:29:40 GMT

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

Siddharth Seth commented on MAPREDUCE-3511:

Also, for jobs which use custom counters (non-optimized) - it would be good to document that
the AM heap may need to be adjusted.
> Counters occupy a good part of AM heap
> --------------------------------------
>                 Key: MAPREDUCE-3511
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3511
>             Project: Hadoop Map/Reduce
>          Issue Type: Sub-task
>          Components: mr-am, mrv2
>    Affects Versions: 0.23.0
>            Reporter: Siddharth Seth
>            Assignee: Vinod Kumar Vavilapalli
>            Priority: Blocker
>             Fix For: 0.23.1
>         Attachments: MAPREDUCE-3511-20120107.1.txt, MAPREDUCE-3511-20120109.txt
> Per task counters seem to be occupying a good part of an AMs heap. Looks like more than
50% of what's used by a TaskAttemptImpl object.
> This could be optimized by interning strings or possibly using mrv1 counters which are
optimized. Currently counters are converted from mrv1 to mrv2 format for in memory storage.
The conversion could be delayed till it's actually required for RPC transfers.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message