[jira] [Created] (YARN-10229) After Enable Yarn-Federation, how to support original client(like that before enable yarn-federation, nothing modified) to submit job to RM directly

["JohnsonGuo (Jira)" <ji...@apache.org>]

JohnsonGuo created YARN-10229:
---------------------------------

             Summary: After Enable Yarn-Federation, how to support original client(like that before enable yarn-federation, nothing modified) to submit job to RM directly
                 Key: YARN-10229
                 URL: https://issues.apache.org/jira/browse/YARN-10229
             Project: Hadoop YARN
          Issue Type: Wish
          Components: amrmproxy, federation, router
    Affects Versions: 3.1.1
            Reporter: JohnsonGuo
         Attachments: ContainerManagerImpl.java

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-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org