SteNicholas opened a new pull request #14332:
URL: https://github.com/apache/flink/pull/14332
## What is the purpose of the change
*`FatalExitExceptionHandler` and `JvmShutdownSafeguard` 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. Enum `ExitCode` should be
introduced that defines all possible exit codes in Flink. The exit codes are
different for `FatalExitExceptionHandler` and `JvmShutdownSafeguard`.*
## Brief change log
- *Add `ExitCode` enum to indicate the associated process exit code.*
- *Change the exit code in `FatalExitExceptionHandler` to be different
from `JvmShutdownSafeguard`.*
## Verifying this change
## Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): (yes / **no**)
- The public API, i.e., is any changed class annotated with
`@Public(Evolving)`: (yes / **no**)
- The serializers: (yes / **no** / don't know)
- The runtime per-record code paths (performance sensitive): (yes / **no**
/ don't know)
- Anything that affects deployment or recovery: JobManager (and its
components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (yes / **no** /
don't know)
- The S3 file system connector: (yes / **no** / don't know)
## Documentation
- Does this pull request introduce a new feature? (yes / **no**)
- If yes, how is the feature documented? (**not applicable** / docs /
JavaDocs / not documented)
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
