hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Graves (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-4361) Fix detailed metrics for protobuf-based RPC on 0.23
Date Mon, 25 Jun 2012 14:39:44 GMT

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

Thomas Graves updated MAPREDUCE-4361:
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 0.23.3
           Status: Resolved  (was: Patch Available)

I committed this to branch 0.23, the change is not applicable to trunk or branch-2 since it
already works there.
                
> 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
>             Fix For: 0.23.3
>
>         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

        

Mime
View raw message