Details
-
Bug
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
3.2.1
-
None
Description
Sometimes when the scheduler tries to cancel a task right after it launches that task on the executor, the KillTask and LaunchTask events can come in a reversed order, causing the task to escape the kill-task signal and finish "secretly". And those tasks even show as an un-launched task in Spark UI.