[
https://issues.apache.org/jira/browse/YARN-11901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18041430#comment-18041430
]
Istvan Toth commented on YARN-11901:
------------------------------------
{quote}should clusters refuse to start if this flag is set? stops people
thinking it is working.
{quote}
{quote}meanwhile, trunk release on older versions should warn on startup that
the feature will go away
{quote}
I think both are good ideas.
One problem with running the above check is that it's gonna emit a warning.
However, if we're only checking if the feature is turned off, and refuse to run
if it's unavalable anyway, it's probably not an issue.
> Remove SecurityManager implementation from YARN
> -----------------------------------------------
>
> Key: YARN-11901
> URL: https://issues.apache.org/jira/browse/YARN-11901
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Ferenc Erdelyi
> Priority: Major
>
> YARN-5280 allowed containers to run with JavaSecurityManager, which is
> permanently disabled as of JDK24 - JEP486.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
