[SPARK-2947] DAGScheduler resubmit the stage into an infinite loop#1877
[SPARK-2947] DAGScheduler resubmit the stage into an infinite loop#1877witgo wants to merge 2 commits intoapache:masterfrom
Conversation
|
QA tests have started for PR 1877. This patch merges cleanly. |
|
QA results for PR 1877: |
|
@witgo can you explain how this happens and why the fix works, and add a unit test for it? We can't really merge something like this without a test. |
There was a problem hiding this comment.
@mateiz
There is no cancel running tasks in the stage . When any one of the running tasks which throws an exception.The following code will be repeated.
failedStages += failedStage
failedStages += mapStageStage will be unnecessary resubmit by resubmitFailedStages
|
It takes some time to add a test for this. |
|
QA tests have started for PR 1877. This patch merges cleanly. |
|
QA results for PR 1877: |
|
@witgo Could you rebase this PR onto master? There are some conflict right now. |
|
QA tests have started for PR 1877 at commit
|
|
QA tests have finished for PR 1877 at commit
|
|
@rxin could you take a look at this PR? Thanks! |
|
Can you explain what problem you are seeing? |
|
QA tests have started for PR 1877 at commit
|
|
SPARK-3224 is the same problem. |
There was a problem hiding this comment.
can you change this and/or the name for the test at line 438? They are currently almost identical such that it's unclear what the point of each test is.
|
QA tests have finished for PR 1877 at commit
|
089577f to
bf6f81a
Compare
|
QA tests have started for PR 1877 at commit
|
|
QA tests have finished for PR 1877 at commit
|
There was a problem hiding this comment.
@rxin Because there is no cancel running tasks in the stage. stage.pendingTasks.contains(task) is necessary.
|
QA tests have started for PR 1877 at commit
|
There was a problem hiding this comment.
once you put this within the conditional statement, only one executor failure will be handled for each stage. that means if there are two executor fails, the 2nd one gets ignored by the dagscheduler, isn't it?
There was a problem hiding this comment.
@rxin Yes, here is unnecessary modifications to processing logic, I negligence.
是的,这里处理逻辑被不必要的修改了,疏忽了.
|
QA tests have finished for PR 1877 at commit
|
|
QA tests have started for PR 1877 at commit
|
|
QA tests have finished for PR 1877 at commit
|
…der (apache#1877) Parquet footer metadata is now always read twice in vectorized parquet reader. When the NameNode is under high pressure, it will cost time to read twice. Actually we can avoid reading the footer twice by reading all row groups in advance and filter row groups according to filters that require push down (no need to read the footer metadata again the second time). Reduce the reading of footer in vectorized parquet reader no existing tests Closes apache#39950 from yabola/skip_footer. Authored-by: chenliang.lu <marssss2929@gmail.com> Signed-off-by: Chao Sun <sunchao@apple.com> Co-authored-by: chenliang.lu <marssss2929@gmail.com>

No description provided.