[FLINK-15156] Warn user if System.exit() is called in user code

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 1.13.0
• Component/s: Runtime / Coordination
• Labels: pull-request-available starter

Release Note

A new configuration value `cluster.intercept-user-system-exit` allows to log a warning, or throw an exception if user code calls "System.exit()".

This feature is not covering all locations in Flink where user code is executed. It just adds the infrastructure for such an interception.

• Assignee: Hwanju Kim
• Reporter: Robert Metzger
• Created: 09/Dec/19 12:53
• Updated: 28/May/21 07:10
• Resolved: 18/Jan/21 19:00

Description

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.

Issue Links

• relates to: FLINK-21307 Revisit activation model of FlinkSecurityManager
• relates to: FLINK-21306 FlinkSecurityManager might avoid fatal system exits
• links to: GitHub Pull Request #14499