You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Yun Gao (Jira)" <ji...@apache.org> on 2022/04/13 06:28:04 UTC

[jira] [Updated] (FLINK-21307) Revisit activation model of FlinkSecurityManager

     [ https://issues.apache.org/jira/browse/FLINK-21307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yun Gao updated FLINK-21307:
----------------------------
    Fix Version/s: 1.16.0

> 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: Minor
>              Labels: auto-deprioritized-critical, auto-deprioritized-major
>             Fix For: 1.15.0, 1.16.0
>
>
> 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.1#820001)