Uploaded image for project: 'Apache Tez'
  1. Apache Tez
  2. TEZ-289

DAGAppMasterShutdownHook should not report KILLED when exception brings down AM

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 0.3.0
    • 0.3.0
    • None

    Description

      when DAGAppMasterShutdownHook is called while dag is in RUNNING it leads to report of KILLED.
      This is misleading as KILLED generally implies that a user-initiated kill occured.

      Better would be to report INTERNAL_ERROR.

      Attachments

        1. TEZ-289.1.patch
          3 kB
          Tsuyoshi Ozawa
        2. TEZ-289.2.patch
          0.9 kB
          Tsuyoshi Ozawa

        Issue Links

        relates to

        Bug - A problem which impairs or prevents the functions of the product. TEZ-141 DAG does not kill running vertices when going into failed state

        • Major - Major loss of function.
        • Resolved

        Bug - A problem which impairs or prevents the functions of the product. TEZ-36 TaskScheduler should not unregister from the RM when sent a reboot

        • Major - Major loss of function.
        • Closed

        Bug - A problem which impairs or prevents the functions of the product. TEZ-676 Tez job fails on client side if nodemanager running AM is lost

        • Major - Major loss of function.
        • Closed

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

          People

            ozawa Tsuyoshi Ozawa
            mikeliddell Mike Liddell
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment