[
https://issues.apache.org/jira/browse/FLINK-11534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ufuk Celebi closed FLINK-11534.
-------------------------------
Resolution: Fixed
Fix Version/s: 1.9.0
> Don't exit JVM after job termination with standalone job
> --------------------------------------------------------
>
> Key: FLINK-11534
> URL: https://issues.apache.org/jira/browse/FLINK-11534
> Project: Flink
> Issue Type: New Feature
> Components: Runtime / Coordination
> Affects Versions: 1.7.0, 1.8.0
> Reporter: Ufuk Celebi
> Assignee: Ufuk Celebi
> Priority: Minor
> Labels: pull-request-available
> Fix For: 1.9.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> If a job deployed in job cluster mode terminates, the JVM running the
> StandaloneJobClusterEntryPoint will exit via System.exit(1).
> When managing such a job this requires access to external systems for logging
> in order to get more details about failure causes or final termination status.
> I believe that there is value in having a StandaloneJobClusterEntryPoint
> option that does not exit the JVM after the job has terminated. This allows
> users to gather further information if they are monitoring the job and
> manually tear down the process.
> If there is agreement to have this feature, I would provide the
> implementation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
