spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Hamstra (JIRA)" <>
Subject [jira] [Created] (SPARK-17769) Some FetchFailure refactoring in the DAGScheduler
Date Mon, 03 Oct 2016 18:51:20 GMT
Mark Hamstra created SPARK-17769:

             Summary: Some FetchFailure refactoring in the DAGScheduler
                 Key: SPARK-17769
             Project: Spark
          Issue Type: Improvement
          Components: Scheduler
            Reporter: Mark Hamstra
            Assignee: Mark Hamstra
            Priority: Minor

SPARK-17644 opened up a discussion about further refactoring of the DAGScheduler's handling
of FetchFailure events.  These include:
* rewriting code and comments to improve readability
* doing fetchFailedAttemptIds.add(stageAttemptId) even when disallowStageRetryForTest is true
* issuing a ResubmitFailedStages event based on whether one is already enqueued for the current
failed stage, not any prior failed stage
* logging the resubmission of all failed stages 

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message