[
https://issues.apache.org/jira/browse/SPARK-58616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wenchen Fan resolved SPARK-58616.
---------------------------------
Fix Version/s: 4.4.0
Resolution: Fixed
Issue resolved by pull request 57824
[https://github.com/apache/spark/pull/57824]
> Attribute a reason for context-wide job cancellation in cancelAllJobs
> ---------------------------------------------------------------------
>
> Key: SPARK-58616
> URL: https://issues.apache.org/jira/browse/SPARK-58616
> Project: Spark
> Issue Type: Improvement
> Components: PySpark, Spark Core
> Affects Versions: 4.3.0
> Reporter: Ganesha S
> Assignee: Ganesha S
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.4.0
>
>
> When a context-wide cancellation fires, every job caught by it fails with the
> fixed message:
> {noformat}
> [SPARK_JOB_CANCELLED] Job <id> cancelled as part of cancellation of all jobs
> {noformat}
> That says what happened, but not who triggered it or why. It is also reported
> dentically on jobs that were perfectly healthy and are only being aborted as
> collateral for someone else's cancellation, so when reading logs, a
> context-wide cancel cannot be distinguished from a genuine failure of the job
> in question. This makes investigating this class of failure slow.
> The sibling cancellation APIs already solve this: SPARK-19549 added an
> optional reason to {{cancelJob}} / {{{}cancelStage{}}}, and SPARK-48900 added
> one to {{cancelJobGroup}} and {{{}cancelJobsWithTag{}}}. {{cancelAllJobs}} is
> the remaining cancellation entry point with no way to attribute intent, and,
> unlike its siblings, it does not even log its invocation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
