hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Weiwei Yang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-6355) Preprocessor framework for AM and Client interactions with the RM
Date Mon, 04 Dec 2017 09:37:00 GMT

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

Weiwei Yang commented on YARN-6355:

Hi [~asuresh]

One question, if user specifies several processors in the chain by property {{yarn.resourcemanager.application-master-service.processors}},
e.g P1, P2, P3. The actual chain seems to be defined as

P1 -> P2 -> P3 -> DefaultAMSProcessor

Why {{DefaultAMSProcessor}} should be the last one in the chain? With the context of opportunistic
containers, isn't it making more sense to re-order to

DefaultAMSProcessor -> P1 -> P2 -> P3

so that guaranteed containers always get allocated first?


> Preprocessor framework for AM and Client interactions with the RM
> -----------------------------------------------------------------
>                 Key: YARN-6355
>                 URL: https://issues.apache.org/jira/browse/YARN-6355
>             Project: Hadoop YARN
>          Issue Type: Improvement
>            Reporter: Arun Suresh
>            Assignee: Arun Suresh
>              Labels: amrmproxy, resourcemanager
>         Attachments: YARN-6355-one-pager.pdf, YARN-6355.001.patch, YARN-6355.002.patch,
YARN-6355.003.patch, YARN-6355.004.patch, YARN-6355.005.patch, YARN-6355.006.patch, YARN-6355.007.patch
> Currently on the NM, we have the {{AMRMProxy}} framework to intercept the AM <->
RM communication and enforce policies. This is used both by YARN federation (YARN-2915) as
well as Distributed Scheduling (YARN-2877).
> This JIRA proposes to introduce a similar framework on the the RM side, so that pluggable
policies can be enforced on ApplicationMasterService centrally as well.
> This would be similar in spirit to a Java Servlet Filter Chain. Where the order of the
interceptors can declared externally.
> Once possible usecase would be:
> the {{OpportunisticContainerAllocatorAMService}} is implemented as a wrapper over the
{{ApplicationMasterService}}. It would probably be better to implement it as an Interceptor.

This message was sent by Atlassian JIRA

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

View raw message