[
https://issues.apache.org/jira/browse/FLINK-21307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-21307:
-----------------------------------
Labels: auto-deprioritized-critical auto-deprioritized-major
auto-deprioritized-minor (was: auto-deprioritized-critical
auto-deprioritized-major stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> Revisit activation model of FlinkSecurityManager
> ------------------------------------------------
>
> Key: FLINK-21307
> URL: https://issues.apache.org/jira/browse/FLINK-21307
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Task
> Affects Versions: 1.13.0
> Reporter: Robert Metzger
> Priority: Not a Priority
> Labels: auto-deprioritized-critical, auto-deprioritized-major,
> auto-deprioritized-minor
>
> In FLINK-15156, we introduced a feature that allows users to log or
> completely disable calls to System.exit(). This feature is enabled for
> certain threads / code sections intended to execute user-code.
> The activation of the security manager (for monitoring user calls to
> System.exit() is currently not well-defined, and only implemented on a
> best-effort basis.
> This ticket is to revisit the activation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
