ahshahid commented on code in PR #50033:
URL: https://github.com/apache/spark/pull/50033#discussion_r1978390638
##########
core/src/test/scala/org/apache/spark/scheduler/DAGSchedulerSuite.scala:
##########
@@ -81,6 +81,15 @@ class DAGSchedulerEventProcessLoopTester(dagScheduler:
DAGScheduler)
}
}
+ def postInCurrentThread(event: DAGSchedulerEvent): Unit = {
Review Comment:
@attilapiros .. It is right that DagScheduler processes the events
sequentially, but in case of failure, it delegates it to another thread pool,
causing asynchronicity.
The reason for the test using asynchroncity in the even loop, is just to be
able to simulate the issue with the given constraints of being unable to
control the behaviour of the event pool emebedded withthin the DagScheduler
itself.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
