[
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 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.
> 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: Minor
> Labels: auto-deprioritized-major, stale-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)
