[
https://issues.apache.org/jira/browse/FLINK-20425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated FLINK-20425:
-----------------------------------
Labels: pull-request-available (was: )
> Change exit code in FatalExitExceptionHandler to be different from
> JvmShutdownSafeguard
> ---------------------------------------------------------------------------------------
>
> Key: FLINK-20425
> URL: https://issues.apache.org/jira/browse/FLINK-20425
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Affects Versions: 1.13.0
> Reporter: Robert Metzger
> Assignee: Nicholas Jiang
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.13.0
>
>
> Both classes mentioned in the title use the same exit code (-17), making it
> impossible to distinguish the cause of an unexpected Flink JVM exit based on
> the exit code alone.
> Maybe we could introduce an Enum that defines all possible exit codes in
> Flink?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
