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

Rename variables in SchedulerNode to reduce ambiguity post YARN-1011

VotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 2.8.0
    • 2.9.0, 3.0.0-alpha1
    • scheduler
    • None
    • 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

        is depended upon by

        Sub-task - The sub-task of the issue YARN-4511 Common scheduler changes to support scheduler-specific oversubscription implementations

        • Major - Major loss of function.
        • Resolved

        Improvement - An improvement or enhancement to an existing feature or task. YARN-5215 Scheduling containers based on external load in the servers

        • Major - Major loss of function.
        • Patch Available

        Activity
          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            elgoiri Íñigo Goiri
            kasha Karthik Kambatla
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment