[
https://issues.apache.org/jira/browse/FLINK-15156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17216875#comment-17216875
]
Hwanju Kim commented on FLINK-15156:
------------------------------------
For 3, definitely small effort. I was just curious about what usecase you have
seen with the concern. I agree and I think we should add this option as well.
I will rebase the current one onto the mainline to prepare for the review. For
2, I think I would leave the current instrumentation as is, while expecting
addition/removal to be done, which should be easy, during the review.
> Warn user if System.exit() is called in user code
> -------------------------------------------------
>
> Key: FLINK-15156
> URL: https://issues.apache.org/jira/browse/FLINK-15156
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Reporter: Robert Metzger
> Priority: Minor
> Labels: starter
>
> It would make debugging Flink errors easier if we would intercept and log
> calls to System.exit() through the SecurityManager.
> A user recently had an error where the JobManager was shutting down because
> of a System.exit() in the user code:
> https://lists.apache.org/thread.html/b28dabcf3068d489f38399c456c80d48569fcdf74b15f8bb95d532d0%40%3Cuser.flink.apache.org%3E
> If I remember correctly, we had such issues before.
> I put this ticket into the "Runtime / Coordination" component, as it is
> mostly about improving the usability / debuggability in that area.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
