[
https://issues.apache.org/jira/browse/MAPREDUCE-3511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13165485#comment-13165485
]
Siddharth Seth commented on MAPREDUCE-3511:
-------------------------------------------
Good point. Calls to getTaskReports (all maps / all reduces) would cause AM
heap usage to go up significantly. Don't think there's any call which asks for
all task counters. Changing to mrv1 would also impact the UI components.
Interning strings is still worth exploring though - not sure how well it will
work with protocol buffers. Alternately try optimizing mrv2 counters or somehow
send mrv1 counters over rpc.
> 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: Bug
> Components: mr-am, mrv2
> Affects Versions: 0.23.0
> Reporter: Siddharth Seth
> Assignee: Devaraj K
>
> 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
