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

Service-user cost shouldn't be accumulated to totalDecayedCallCost and totalRawCallCost.

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 3.4.0
    • 3.4.0
    • ipc
    • None
    • Reviewed

    Description

      HADOOP-17165 has introduced a very useful feature: service-user. After this feature I think we shouldn't add the service-user's cost into totalDecayedCallCost and totalRawCallCost anymore. Because it may give all the identities the priority 0(Supposing we have a big service-user).

      Attachments

        1. HADOOP-17280.001.patch
          0.9 kB
          Jinglun
        2. HADOOP-17280.002.patch
          3 kB
          Jinglun
        3. HADOOP-17280.003.patch
          9 kB
          Jinglun
        4. HADOOP-17280.004.patch
          9 kB
          Jinglun
        5. HADOOP-17280.005.patch
          12 kB
          Jinglun
        6. HADOOP-17280.006.patch
          12 kB
          Jinglun

        Issue Links

          relates to

          New Feature - A new feature of the product, which has yet to be developed. HADOOP-17165 Implement service-user feature in DecayRPCScheduler

          • Major - Major loss of function.
          • Resolved

          Activity

            People

              LiJinglun Jinglun
              LiJinglun Jinglun
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: