hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hitesh Shah (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (YARN-1593) support out-of-proc AuxiliaryServices
Date Wed, 09 Nov 2016 18:55:59 GMT

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

Hitesh Shah edited comment on YARN-1593 at 11/9/16 6:55 PM:
------------------------------------------------------------

[~vvasudev] One question on the design doc. The doc does not seem to cover how user applications
can define dependencies on these system services. For example, how to ensure that an MR/Tez/xyz
container that requires the shuffle service does not get launched on a node where the system
service is not running. This has 2 aspects - firstly how to ensure container allocations happen
on correct nodes where these services are running and secondly, the service might be down
when the container actually gets launched and therefore how the behavior will change as a
result ( does the container eventually fail, does the NM itself stop the launch of the container
and send an error back, etc).

Is this something that will be looked at later or should it be designed for from now itself
to simplify the use of system services for user applications? 


was (Author: hitesh):
[~vvasudev] One question on the design doc. The doc does not seem to cover how user applications
can define dependencies on these system services. For example, how to ensure that an MR/Tez/xyz
container that requires the shuffle service does not get launched on a node where the system
service is not running. This has 2 aspects - firstly how to ensure container allocations happen
on correct nodes where these services are running and secondly, the service might be down
when the container actually gets launched and therefore how the behavior will change as a
result ( does the container eventually fail, does the NM itself stop the launch of the container
and send an error back, etc).

> support out-of-proc AuxiliaryServices
> -------------------------------------
>
>                 Key: YARN-1593
>                 URL: https://issues.apache.org/jira/browse/YARN-1593
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: nodemanager, rolling upgrade
>            Reporter: Ming Ma
>            Assignee: Varun Vasudev
>         Attachments: SystemContainersandSystemServices.pdf
>
>
> AuxiliaryServices such as ShuffleHandler currently run in the same process as NM. There
are some benefits to host them in dedicated processes.
> 1. NM rolling restart. If we want to upgrade YARN , NM restart will force the ShuffleHandler
restart. If ShuffleHandler runs as a separate process, ShuffleHandler can continue to run
during NM restart. NM can reconnect the the running ShuffleHandler after restart.
> 2. Resource management. It is possible another type of AuxiliaryServices will be implemented.
AuxiliaryServices are considered YARN application specific and could consume lots of resources.
Running AuxiliaryServices in separate processes allow easier resource management. NM could
potentially stop a specific AuxiliaryServices process from running if it consumes resource
way above its allocation.
> Here are some high level ideas:
> 1. NM provides a hosting process for each AuxiliaryService. Existing AuxiliaryService
API doesn't change.
> 2. The hosting process provides RPC server for AuxiliaryService proxy object inside NM
to connect to.
> 3. When we rolling restart NM, the existing AuxiliaryService processes will continue
to run. NM could reconnect to the running AuxiliaryService processes upon restart.
> 4. Policy and resource management of AuxiliaryServices. So far we don't have immediate
need for this. AuxiliaryService could run inside a container and its resource utilization
could be taken into account by RM and RM could consider a specific type of applications overutilize
cluster resource.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message