Uploaded image for project: 'Hama'
  1. Hama
  2. HAMA-936

Occasional yarn job fails with timeout exception

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 0.6.4
    • Fix Version/s: 0.7.0
    • Component/s: yarn
    • Labels:
      None

      Description

      Reported summary: Job has finished successfully but no containers. So finally, job throws FAILED status with timeout exception.

      What happen if the getContainerStatuses only returns the current container statuses? In other words, if the getContainerStatuses doesn't care about the completed containers, logic of JobImpl.startJob() implementation is very unstable.

        Attachments

          Activity

            People

            • Assignee:
              conquestor Minho Kim
              Reporter:
              udanax Edward J. Yoon
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: