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

Vinod Kumar Vavilapalli commented on YARN-2571:
-----------------------------------------------

Apologies for coming in really late on this.

bq. startup: create the /services and /users paths with system ACLs (yarn, hdfs 
principals)
bq. app-launch: create the user directory /users/$username with the relevant 
permissions (CRD) for them to create subnodes.
None of this is RM responsibility. Similar to creation of user directories on 
HDFS, this needs to be taken care of by administrators/external systems.

bq. bq. attempt, container, app completion: remove service records with the 
matching persistence and ID
This looks like application-level responsibility. Removing records on 
container-completion can and should be done by the individual apps' 
ApplicationMasters. Removing records on app completion should be done in an 
application-cleanup container (YARN-2261). Any use-case for application-attempt 
level records?

> RM to support YARN registry 
> ----------------------------
>
>                 Key: YARN-2571
>                 URL: https://issues.apache.org/jira/browse/YARN-2571
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>         Attachments: YARN-2571-001.patch, YARN-2571-002.patch, 
> YARN-2571-003.patch, YARN-2571-005.patch, YARN-2571-007.patch, 
> YARN-2571-008.patch, YARN-2571-009.patch
>
>
> The RM needs to (optionally) integrate with the YARN registry:
> # startup: create the /services and /users paths with system ACLs (yarn, hdfs 
> principals)
> # app-launch: create the user directory /users/$username with the relevant 
> permissions (CRD) for them to create subnodes.
> # attempt, container, app completion: remove service records with the 
> matching persistence and ID



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

Reply via email to