[
https://issues.apache.org/jira/browse/HADOOP-13285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15337170#comment-15337170
]
Hudson commented on HADOOP-13285:
---------------------------------
SUCCESS: Integrated in Hadoop-trunk-Commit #9980 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/9980/])
HADOOP-13285. DecayRpcScheduler MXBean should only report decayed (xyao: rev
0761379fe45898c44c8f161834c298ef932e4d8c)
*
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/ipc/DecayRpcScheduler.java
*
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/ipc/TestDecayRpcScheduler.java
> 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: [email protected]
For additional commands, e-mail: [email protected]
