Uploaded image for project: 'Spark'
  1. Spark
  2. SPARK-20624 SPIP: Add better handling for node shutdown
  3. SPARK-36614

Executor loss reason shows "worker lost" rather "Executor decommission"

Log workAgile BoardRank to TopRank to BottomAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersConvert to IssueMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete CommentsDelete
    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 3.1.2, 3.2.0, 3.3.0
    • 3.2.0, 3.1.3
    • Spark Core
    • None

    Description

      For a lost executor caused by decommission, the loss reason shows "worker lost", while it is actually due to decommission.

      Attachments

        Issue Links

        causes

        Sub-task - The sub-task of the issue SPARK-38023 ExecutorMonitor.onExecutorRemoved should handle ExecutorDecommission as finished

        • Major - Major loss of function.
        • Resolved
        links to

        Pull request #33868 [Github] Pull Request #33868 (Ngone51)

        Pull request #33868 [Github] Pull Request #33868 (Ngone51)

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

          People

            Ngone51 wuyi Assign to me
            Ngone51 wuyi
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment