hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Li Lu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-2102) More generalized timeline ACLs
Date Mon, 15 Sep 2014 18:58:36 GMT

    [ https://issues.apache.org/jira/browse/YARN-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14134325#comment-14134325
] 

Li Lu commented on YARN-2102:
-----------------------------

Hi [~zjshen], just a quick thing to check, shall we use the lock map in the existing leveldbstore
here? Seems like some operations need to acquire locks? 

> More generalized timeline ACLs
> ------------------------------
>
>                 Key: YARN-2102
>                 URL: https://issues.apache.org/jira/browse/YARN-2102
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Zhijie Shen
>            Assignee: Zhijie Shen
>         Attachments: GeneralizedTimelineACLs.pdf, YARN-2102.1.patch, YARN-2102.2.patch,
YARN-2102.3.patch, YARN-2102.5.patch
>
>
> We need to differentiate the access controls of reading and writing operations, and we
need to think about cross-entity access control. For example, if we are executing a workflow
of MR jobs, which writing the timeline data of this workflow, we don't want other user to
pollute the timeline data of the workflow by putting something under it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message