Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-13285

DecayRpcScheduler MXBean should only report decayed CallVolumeSummary

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.8.0, 3.0.0-alpha1
    • Component/s: ipc
    • Labels:
      None
    • Target Version/s:
    • Hadoop Flags:
      Reviewed

      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]}"
      

        Attachments

          Activity

            People

            • Assignee:
              xyao Xiaoyu Yao
              Reporter:
              nmaheshwari Namit Maheshwari
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: