You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Xiaoyu Yao (JIRA)" <ji...@apache.org> on 2016/06/16 22:01:05 UTC
[jira] [Moved] (HADOOP-13285) DecayRpcScheduler MXBean should only
report decayed CallVolumeSummary
[ https://issues.apache.org/jira/browse/HADOOP-13285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xiaoyu Yao moved HDFS-10539 to HADOOP-13285:
--------------------------------------------
Component/s: (was: ipc)
ipc
Key: HADOOP-13285 (was: HDFS-10539)
Project: Hadoop Common (was: Hadoop HDFS)
> 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
>
> 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" : "{\"hrt_qa\":[1,2]}"
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org