[ 
https://issues.apache.org/jira/browse/YARN-2571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Steve Loughran updated YARN-2571:
---------------------------------
    Attachment: YARN-2571-005.patch

Patch 005.
# in sync with trunk rev 0942c9
# moved the path creation logic in the {{RegistryAdminService.start()}} 
operation to being async
# tests enhanced to await completion of async setup.

The reason to move to async is to eliminate the impact of ZK connection 
problems on RM startup. With this patch all RM->registry operations are 
executed in a single executor thread, which implicitly queues the requests in 
an ordered sequence. 

There is one side-effect: if there is a failure in registry startup due to 
security problems, this is not propagated to the RM —i.e. it does not cause RM 
startup to fail. It will however be visible to users of the registry who 
themselves are likely to have auth problems.

> 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
>
>
> 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