[jira] [Closed] (FLINK-10948) Add option to write out termination message with application status

["Till Rohrmann (Jira)" <ji...@apache.org>]

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

Till Rohrmann closed FLINK-10948.
---------------------------------
    Resolution: Abandoned

Closed for inactivity.

> Add option to write out termination message with application status
> -------------------------------------------------------------------
>
>                 Key: FLINK-10948
>                 URL: https://issues.apache.org/jira/browse/FLINK-10948
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Coordination
>            Reporter: Ufuk Celebi
>            Assignee: Ufuk Celebi
>            Priority: Minor
>
> I propose to add an option to write out a termination message to a file that indicates the terminal application status. With the change proposed in FLINK-10743, we can't use the exit code to differentiate between cancelled and succeeded applications.
> The motivating use case for both this ticket and FLINK-10743 are Flink job clusters ({{StandaloneJobClusterEntryPoint}}) with Kubernetes. The idea of the termination message comes from Kubernetes ([https://kubernetes.io/docs/tasks/debug-application-cluster/determine-reason-pod-failure/)]. 
> With this in place a terminated Pod will report the final status as in:
> {code:java}
> state:
>   terminated:
>     exitCode: 0
>     finishedAt: 2018-11-20T11:00:59Z
>     message: CANCELED # <--- termination message
>     reason: Completed
>     startedAt: 2018-11-20T10:59:18Z
> {code}
> The implementation could be done in {{ClusterEntrypoint#runClusterEntrypoint(ClusterEntrypoint)}} which is used by all entry points to run Flink.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)