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

Xiaoyu Yao updated HADOOP-13285:
--------------------------------
          Resolution: Fixed
        Hadoop Flags: Reviewed
       Fix Version/s: 2.8.0
    Target Version/s: 2.8.0
              Status: Resolved  (was: Patch Available)

Thank [~jnp] for the review. I've commit the patch to trunk, branch-2 and 
branch-2.8.

> DecayRpcScheduler MXBean should only report decayed CallVolumeSummary
> ---------------------------------------------------------------------
>
>                 Key: HADOOP-13285
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13285
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: ipc
>            Reporter: Namit Maheshwari
>            Assignee: Xiaoyu Yao
>             Fix For: 2.8.0
>
>         Attachments: HADOOP-13285.00.patch
>
>
> HADOOP-13197 added non-decayed call metrics in metrics2 source for 
> DecayedRpcScheduler. However, CallVolumeSummary in MXBean was affected 
> unexpectedly to include both decayed and non-decayed call volume. The root 
> cause is Jackson ObjectMapper simply serialize all the content of the 
> callCounts map which contains both non-decayed and decayed counter after 
> HADOOP-13197. This ticket is opened to fix the CallVolumeSummary in MXBean to 
> include only decayed call volume for backward compatibility and add unit test 
> for DecayRpcScheduler MXBean to catch this in future. 
> CallVolumeSummary JMX example before HADOOP-13197
> {code}
> "CallVolumeSummary" : "{\"hbase\":1,\"mapred\":1}"
> {code}
>  CallVolumeSummary JMX example after HADOOP-13197
> {code}
> "CallVolumeSummary" : "{\"user_x\":[1,2]}"
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org

Reply via email to