Uploaded image for project: 'Hadoop YARN'
  1. Hadoop YARN
  2. YARN-4718

Rename variables in SchedulerNode to reduce ambiguity post YARN-1011

Log workAgile BoardRank to TopRank to BottomAttach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

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

      Description

      As discussed in YARN-1011, we are planning to add a few more variables regarding utilization to SchedulerNode. To ensure the new variables are descriptive and don't lead to confusion, the existing variables could use some renaming.

        Attachments

        1. YARN-4718-v000.patch
          103 kB
          Íñigo Goiri
        2. YARN-4718-v001.patch
          110 kB
          Íñigo Goiri
        3. YARN-4718-v002.patch
          114 kB
          Íñigo Goiri
        4. YARN-4718-v003.patch
          115 kB
          Íñigo Goiri
        5. YARN-4718-v004.patch
          82 kB
          Íñigo Goiri

        Issue Links

          Activity

          $i18n.getText('security.level.explanation', $currentSelection) Viewable by All Users
          Cancel

            People

            • Assignee:
              elgoiri Íñigo Goiri Assign to me
              Reporter:
              kasha Karthik Kambatla

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment