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

[History Server]Only one replay thread of FsHistoryProvider work because of straggler

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

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 2.4.4
    • 3.0.0
    • Spark Core
    • None

    Description

      As shown in the attachment, we set spark.history.fs.numReplayThreads=30 for spark history server.
      However, there is only one replay thread work because of straggler.

      Let's check the code.
      https://github.com/apache/spark/blob/7f36cd2aa5e066a807d498b8c51645b136f08a75/core/src/main/scala/org/apache/spark/deploy/history/FsHistoryProvider.scala#L509-L547

      There is a synchronous operation for all replay tasks.

      Attachments

        Issue Links

        is related to

        Bug - A problem which impairs or prevents the functions of the product. SPARK-39083 Fix FsHistoryProvider race condition between update and clean app data

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

        Web Link GitHub Pull Request #25797

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

          People

            hzfeiwang feiwang Assign to me
            hzfeiwang feiwang
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment