Hadoop Common
  1. Hadoop Common
  2. HADOOP-4305

repeatedly blacklisted tasktrackers should get declared dead

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.20.0
    • Component/s: None
    • Labels:
      None
    • Hadoop Flags:
      Reviewed
    • Release Note:
      Improved TaskTracker blacklisting strategy to better exclude faulty tracker from executing tasks.

      Description

      When running a batch of jobs it often happens that the same tasktrackers are blacklisted again and again. This can slow job execution considerably, in particular, when tasks fail because of timeout.
      It would make sense to no longer assign any tasks to such tasktrackers and to declare them dead.

      1. patch-4305-0.18.txt
        21 kB
        Amareshwari Sriramadasu
      2. patch-4305-1.txt
        21 kB
        Amareshwari Sriramadasu
      3. patch-4305-2.txt
        29 kB
        Amareshwari Sriramadasu
      4. patch-4305-3.txt
        31 kB
        Amareshwari Sriramadasu
      5. patch-4305-4.txt
        37 kB
        Amareshwari Sriramadasu

        Issue Links

          Activity

          Christian Kunz created issue -
          dhruba borthakur made changes -
          Field Original Value New Value
          Link This issue is related to HADOOP-2676 [ HADOOP-2676 ]
          Devaraj Das made changes -
          Fix Version/s 0.20.0 [ 12313438 ]
          Assignee Amareshwari Sriramadasu [ amareshwari ]
          Amar Kamat made changes -
          Link This issue is related to HADOOP-2175 [ HADOOP-2175 ]
          Amareshwari Sriramadasu made changes -
          Attachment patch-4305-1.txt [ 12393865 ]
          Amareshwari Sriramadasu made changes -
          Status Open [ 1 ] Patch Available [ 10002 ]
          Amareshwari Sriramadasu made changes -
          Attachment patch-4305-0.18.txt [ 12394052 ]
          Amareshwari Sriramadasu made changes -
          Status Patch Available [ 10002 ] Open [ 1 ]
          Amareshwari Sriramadasu made changes -
          Attachment patch-4305-2.txt [ 12394532 ]
          Amareshwari Sriramadasu made changes -
          Status Open [ 1 ] Patch Available [ 10002 ]
          Amareshwari Sriramadasu made changes -
          Status Patch Available [ 10002 ] Open [ 1 ]
          Amareshwari Sriramadasu made changes -
          Attachment patch-4305-3.txt [ 12395280 ]
          Amareshwari Sriramadasu made changes -
          Status Open [ 1 ] Patch Available [ 10002 ]
          Release Note Added configuration property "mapred.max.tasktracker.blacklists", to specify the number of blacklists for a task tracker by various jobs after which the task tracker can be blacklisted across all jobs, defaults to 4.
          Amareshwari Sriramadasu made changes -
          Attachment patch-4305-4.txt [ 12395393 ]
          Devaraj Das made changes -
          Resolution Fixed [ 1 ]
          Status Patch Available [ 10002 ] Resolved [ 5 ]
          Hadoop Flags [Reviewed]
          Amareshwari Sriramadasu made changes -
          Release Note Added configuration property "mapred.max.tasktracker.blacklists", to specify the number of blacklists for a task tracker by various jobs after which the task tracker can be blacklisted across all jobs, defaults to 4. Improves the blacklisting strategy, whereby, tasktrackers that are blacklisted are not given tasks to run from other jobs, subject to the following conditions (all must be met):
          1) The TaskTracker has been blacklisted by at least 4 jobs ( can be configured by mapred.max.tasktracker.blacklists)
          2) The TaskTracker has been blacklisted 50% more number of times than the average
          3) The cluster has less than 50% trackers blacklisted.
          Once in 24 hours, a TaskTracker blacklisted for all jobs is given a chance.
          Restarting the TaskTracker moves it out of the blacklist.
          Robert Chansler made changes -
          Release Note Improves the blacklisting strategy, whereby, tasktrackers that are blacklisted are not given tasks to run from other jobs, subject to the following conditions (all must be met):
          1) The TaskTracker has been blacklisted by at least 4 jobs ( can be configured by mapred.max.tasktracker.blacklists)
          2) The TaskTracker has been blacklisted 50% more number of times than the average
          3) The cluster has less than 50% trackers blacklisted.
          Once in 24 hours, a TaskTracker blacklisted for all jobs is given a chance.
          Restarting the TaskTracker moves it out of the blacklist.
          Improved TaskTracker blacklisting strategy to better exclude faulty tracker from executing tasks.
          Nigel Daley made changes -
          Status Resolved [ 5 ] Closed [ 6 ]
          Owen O'Malley made changes -
          Component/s mapred [ 12310690 ]

            People

            • Assignee:
              Amareshwari Sriramadasu
              Reporter:
              Christian Kunz
            • Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development