[
https://issues.apache.org/jira/browse/FLINK-9207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-9207:
----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor (was:
auto-deprioritized-major stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> Client returns SUCCESS(0) return code for canceled job
> ------------------------------------------------------
>
> Key: FLINK-9207
> URL: https://issues.apache.org/jira/browse/FLINK-9207
> Project: Flink
> Issue Type: Bug
> Components: Command Line Client
> Affects Versions: 1.5.0
> Environment: Version: 1.5.0, Commit : 2af481a
> Reporter: Amit Jain
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> Flink Client returns zero return code when a job is deliberately canceled.
> Steps to reproduced it:
> 1. bin/flink run -p 10 -m yarn-cluster -yjm 1024 -ytm 12288 WordCount.jar
> 2. User externally canceled the job.
> 3. Job Manager marked the job as CANCELED.
> 4. Although client code emits following logs, still returns zero return code.
> org.apache.hadoop.yarn.client.api.impl.YarnClientImpl - Killed
> application application_1523726493647_.....
> Job scheduler like Airflow would have hard-time detecting whether the
> submitted job was canceled or not.
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
