mridulm commented on pull request #29977: URL: https://github.com/apache/spark/pull/29977#issuecomment-705735424
> You also have other situations where tasks are killed, which luckily I guess the TaskContext does have a isInterrupted field for that. The executor ends up making some pass/fail decisions that go to the scheduler Currently we document `isInterrupted` as a task kill by platform (instead of user code related task failure). Essentially we have: a) Succeeded. b) Failed. b.1) Task killed by platform b.2) Task failed due to user code. Do we want to distinguish b.1 from b.2 explicitly via api ? (`isInterrupted` currently does that - imo that should suffice). Is there any other failure flows ? (ignoring executor crash here). ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
