[jira] [Updated] (YARN-7376) YARN top ACLs
[ https://issues.apache.org/jira/browse/YARN-7376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hung updated YARN-7376: Attachment: YARN-7376.002.patch > YARN top ACLs > - > > Key: YARN-7376 > URL: https://issues.apache.org/jira/browse/YARN-7376 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: Jonathan Hung >Assignee: Jonathan Hung > Attachments: YARN-7376.001.patch, YARN-7376.002.patch > > > Currently YARN top can be invoked by everyone. But we want to avoid a > scenario where random users invoke YARN top, and potentially leave it > running. So we can implement ACLs to prevent this. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7376) YARN top ACLs
[ https://issues.apache.org/jira/browse/YARN-7376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hung updated YARN-7376: Attachment: YARN-7376.001.patch > YARN top ACLs > - > > Key: YARN-7376 > URL: https://issues.apache.org/jira/browse/YARN-7376 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: Jonathan Hung >Assignee: Jonathan Hung > Attachments: YARN-7376.001.patch > > > Currently YARN top can be invoked by everyone. But we want to avoid a > scenario where random users invoke YARN top, and potentially leave it > running. So we can implement ACLs to prevent this. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
