[HADOOP-13285] DecayRpcScheduler MXBean should only report decayed CallVolumeSummary

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.8.0, 3.0.0-alpha1
• Component/s: ipc
• Target Version/s: 2.8.0
• Hadoop Flags: Reviewed
• Assignee: Xiaoyu Yao
• Reporter: Namit Maheshwari
• Created: 16/Jun/16 21:48
• Updated: 30/Aug/16 01:13
• Resolved: 17/Jun/16 22:32

Description

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

"CallVolumeSummary" : "{\"hbase\":1,\"mapred\":1}"

CallVolumeSummary JMX example after HADOOP-13197

"CallVolumeSummary" : "{\"user_x\":[1,2]}"