Uploaded image for project: 'Spark'
  1. Spark
  2. SPARK-12411

Reconsider executor heartbeats rpc timeout

Log workAgile BoardRank to TopRank to BottomAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete CommentsDelete
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 1.6.1, 2.0.0
    • Spark Core
    • None

    Description

      Currently, the timeout for checking when an executor is failed is the same as the timeout of the sender ("spark.network.timeout") which defaults to 120s.

      This means if there is a network issue, the executor only gets one try to heartbeat which probably causes the failure detection to be flaky.

      The executor has a config to control how often to heartbeat (spark.executor.heartbeatInterval) which defaults to 10s. This combination of configs doesn't seem to make sense. The heartbeat rpc timeout should probably be less than or equal to the heartbeatInterval.

      Attachments

        Activity

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

          People

            nongli Nong Li Assign to me
            nongli Nong Li
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment