You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2021/11/09 22:39:00 UTC

[jira] [Updated] (FLINK-15927) TaskExecutor should treat it as a fatal error is Task cannot be failed

     [ https://issues.apache.org/jira/browse/FLINK-15927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Flink Jira Bot updated FLINK-15927:
-----------------------------------
    Labels: auto-deprioritized-major stale-minor  (was: auto-deprioritized-major)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Minor but is unassigned and neither itself nor its Sub-Tasks have been updated for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is still Minor, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized.


> TaskExecutor should treat it as a fatal error is Task cannot be failed
> ----------------------------------------------------------------------
>
>                 Key: FLINK-15927
>                 URL: https://issues.apache.org/jira/browse/FLINK-15927
>             Project: Flink
>          Issue Type: Bug
>          Components: Runtime / Task
>            Reporter: Stephan Ewen
>            Priority: Minor
>              Labels: auto-deprioritized-major, stale-minor
>
> When the TaskManager cannot mark a task as failed, it is only logged as a warning.
> This should instead be treated as a fatal error.
> TaskExecutor line 1419:
> {code}
> try {
> 	task.failExternally(cause);
> } catch (Throwable t) {
> 	log.error("Could not fail task {}.", executionAttemptID, t);
> }
> {code}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)