[
https://issues.apache.org/jira/browse/FLINK-9207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16451910#comment-16451910
]
Chesnay Schepler edited comment on FLINK-9207 at 4/25/18 8:52 AM:
------------------------------------------------------------------
Not sure whether we can change this behavior; it wouldn't surprise me if setups
exist that rely on the client returning 0 on cancellation, in particular for
streaming jobs.
What we could maybe do is explicitly print the final job state in the client.
Currently, if the job is canceled the client still prints {{Job with JobID X
has finished.}}. If instead if printed {{Job with JobID X has canceled.}} You
could grep the state and setup your logic based on that.
was (Author: zentol):
Not sure whether we can change this behavior; it wouldn't surprise me if setups
exist that rely on the client returning 0 on cancellation, in particular for
streaming jobs.
What we could maybe do is explicitly print the final job state in the client.
Currently, if the job is canceled the client still prints {{Job with JobID X
has finished.}}. If instead if printed {{... was canceled.}}You could grep the
state and setup your logic based on that.
> 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: Client
> Affects Versions: 1.5.0
> Environment: Version: 1.5.0, Commit : 2af481a
> Reporter: Amit Jain
> Priority: Blocker
> Fix For: 1.5.0
>
>
> 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
(v7.6.3#76005)
