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

Support rolling back a shuffle map stage and re-generate the shuffle files

Log workAgile BoardRank to TopRank to BottomAttach filesAttach ScreenshotVotersStop watchingWatchersCreate sub-taskConvert to sub-taskLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.0.0
    • Fix Version/s: 3.0.0
    • Component/s: Spark Core
    • Labels:
      None

      Description

      This is a follow up of https://issues.apache.org/jira/browse/SPARK-23243

      To completely fix that problem, Spark needs to be able to rollback a shuffle map stage and rerun all the map tasks.

      According to https://github.com/apache/spark/pull/9214 , Spark doesn't support it currently, as in shuffle writing "first write wins".

      Since overwriting shuffle files is hard, we can extend the shuffle id to include a "shuffle generation number". Then the reduce task can specify which generation of shuffle it wants to read. https://github.com/apache/spark/pull/6648 seems in the right direction.

        Attachments

        Issue Links

          Activity

          $i18n.getText('security.level.explanation', $currentSelection) Viewable by All Users
          Cancel

            People

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment