Details
-
Bug
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
1.0.2, 1.1.2, 1.2.2, 1.3.0
-
None
Description
When a job is submitted with a job group and that job group is inherited from a parent thread, there are multiple bugs that may prevent this job from being cancelable via SparkContext.cancelJobGroup():
- When filtering jobs based on their job group properties, DAGScheduler calls get() instead of getProperty(), which does not respect inheritance, so it will skip over jobs whose groups were inherited.
- Properties objects are mutable, but we do not make defensive copies / snapshots, so modifications of the parent thread's job group will cause running jobs' groups to change.
Both of these issues are easy to fix: use `getProperty()` and perform defensive copying.
Attachments
Issue Links
- blocks
-
SPARK-6862 Add BatchPage to display details about a batch
- Resolved
- links to