Github user jinxing64 commented on the issue:
https://github.com/apache/spark/pull/16620
As @squito mentioned:
>Before this, the DAGScheduler didn't really know anything about
taskSetManagers. (In its current form, this pr uses a "leaked" handle via
rootPool.getSortedTaskSetQueue). Is adding it here a mistake? An alternative
would be to add a method to TaskScheduler like
markTaskSetsForStageAsZombie(stageId: Int). But that is still basically
exposing the idea of "zombie" tasksets to the dagscheduler, I dunno if its
actually any cleaner.
I think this a cleaner and simpler way for fixing this bug. And we can
avoid adding TSM info to the DAGScheduler.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
