You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Jason Lowe (JIRA)" <ji...@apache.org> on 2012/06/22 22:21:43 UTC
[jira] [Updated] (MAPREDUCE-4361) Fix detailed metrics for
protobuf-based RPC on 0.23
[ https://issues.apache.org/jira/browse/MAPREDUCE-4361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Lowe updated MAPREDUCE-4361:
----------------------------------
Attachment: MAPREDUCE-4361.patch
Patch that ports the relevant portions of HADOOP-8085 to branch-0.23. I manually tested this by bringing up a single-node cluster and visiting the ResourceManager JMX page. The detailed metrics for YARN interfaces like {{NodeHeartbeatNumOps}} were non-zero, whereas they were zero before applying this patch.
I also manually ran the unit tests in yarn-common, and they all passed.
> Fix detailed metrics for protobuf-based RPC on 0.23
> ---------------------------------------------------
>
> Key: MAPREDUCE-4361
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4361
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.23.0
> Reporter: Jason Lowe
> Assignee: Jason Lowe
> Attachments: MAPREDUCE-4361.patch
>
>
> RPC detailed metrics for any protobuf-based RPC ports are always zero. ProtoOverHadoopRpcEngine needs the same detailed metric logic as in WritableRpcEngine. This is effectively the same change as in HADOOP-8085 except tailored for branch-0.23 which didn't take the full protobuf branch changes that went into branch-2 and trunk.
--
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