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

Bibin Chundatt commented on YARN-10229:
---------------------------------------

[~BilwaST] /[~122512...@qq.com]

Nodemanagers need to stay independent of the applications . Parsing of 
application specific details are not suggested in nodemanager side.

Alternate Solution:

Currently AMRMProxyService overrides the AMRMToken always. If we could notify 
from interceptors whether the amrmtoken needs to be override , then we should 
be able to submit. In this case the FederationInterceptor could check the 
homeapplications entry is available in federation state store. 

Thoughts??

> [Federation] Client should be able to submit application to RM directly using 
> normal client conf
> ------------------------------------------------------------------------------------------------
>
>                 Key: YARN-10229
>                 URL: https://issues.apache.org/jira/browse/YARN-10229
>             Project: Hadoop YARN
>          Issue Type: Wish
>          Components: amrmproxy, federation
>    Affects Versions: 3.1.1
>            Reporter: JohnsonGuo
>            Assignee: Bilwa S T
>            Priority: Major
>
> Scenario: When enable the yarn federation feature with multi yarn clusters, 
> one can submit their job to yarn-router by *modified* their client 
> configuration with yarn router address.
> But if one still wants to submit their jobs via the original client (before 
> enable federation) to RM directly, it will encounter the AMRMToken exception. 
>  That means once enable federation ,if some one want to submit job, they have 
> to  modify the client conf.
>  
> one possible solution for this Scenario is:
> In NodeManger, when the client ApplicationMaster request comes:
>  * get the client job.xml  from HDFS "".
>  * parse the "yarn.resourcemanager.scheduler.address" parameter in job.xml
>  * if the value of the parameter is "localhost:8049"(AMRM address),then do 
> the AMRMToken valid process
>  * if the value of the parameter is "rm:port"(rm address),then skip the 
> AMRMToken valid process
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

Reply via email to