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

Non-public resource localization on a bad disk causes subsequent containers failure

    Details

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

      Description

      YARN-3591 added the checkLocalResource method to isResourcePresent() call to allow checking an already localized resource against the list of good/full directories.

      Since LocalResourcesTrackerImpl instantiations for app level resources and private resources do not use the new constructor, such resources that are on bad disk will never be checked against good dirs.

        Attachments

        1. YARN-6641.001.patch
          8 kB
          Kuhu Shukla
        2. YARN-6641.002.patch
          8 kB
          Kuhu Shukla
        3. YARN-6641.003.patch
          11 kB
          Kuhu Shukla
        4. YARN-6641.004.patch
          11 kB
          Kuhu Shukla

          Activity

            People

            • Assignee:
              kshukla Kuhu Shukla
              Reporter:
              kshukla Kuhu Shukla
            • Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: