hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Subru Krishnan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-6355) Interceptor framework for the YARN ApplicationMasterService
Date Fri, 17 Mar 2017 19:31:41 GMT

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

Subru Krishnan updated YARN-6355:
---------------------------------
    Issue Type: Sub-task  (was: Improvement)
        Parent: YARN-5468

> Interceptor framework for the YARN ApplicationMasterService
> -----------------------------------------------------------
>
>                 Key: YARN-6355
>                 URL: https://issues.apache.org/jira/browse/YARN-6355
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Arun Suresh
>            Assignee: Arun Suresh
>
> 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
(v6.3.15#6346)

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