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

Application expiration difficult to debug for end-users

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

    Details

      Description

      When an AM attempt expires the AMLivelinessMonitor in the RM will kill the job and mark it as failed. However there are no diagnostic messages set for the application indicating that the application failed because of expiration. Even if the AM logs are examined, it's often not obvious that the application was externally killed. The only evidence of what happened to the application is currently in the RM logs, and those are often not accessible by users.

        Attachments

        1. YARN-227.patch
          7 kB
          Jason Darrell Lowe
        2. YARN-227-branch-0.23.patch
          6 kB
          Jason Darrell Lowe
        3. YARN-227-branch-0.23.patch
          6 kB
          Jason Darrell Lowe
        4. YARN-227.patch
          7 kB
          Jason Darrell Lowe

        Issue Links

          Activity

            People

            • Assignee:
              jlowe Jason Darrell Lowe
              Reporter:
              jlowe Jason Darrell Lowe

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment