[
https://issues.apache.org/jira/browse/YARN-8963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16721969#comment-16721969
]
Billie Rinaldi commented on YARN-8963:
--------------------------------------
+1 for patch 3. I verified that the feature.terminal.enabled flag controls
whether or not a shell can be opened for a container. In the UI, the feature
disabled message is displayed, but at the command line the connection appears
to be closed without the message being displayed. I suspect this is due to
inconsistent flushing after writing to stderr, which I have opened YARN-9129 to
address. Thanks for the patch, [~eyang]!
> Add flag to disable interactive shell
> -------------------------------------
>
> Key: YARN-8963
> URL: https://issues.apache.org/jira/browse/YARN-8963
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Eric Yang
> Assignee: Eric Yang
> Priority: Major
> Attachments: YARN-8963.001.patch, YARN-8963.002.patch,
> YARN-8963.003.patch
>
>
> For some production job, application admin might choose to disable debugging
> to production jobs to prevent developer or system admin from accessing the
> containers. It would be nice to add an environment variable flag to disable
> interactive shell during application submission.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
