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

Jin Yibo updated MAPREDUCE-7044:
--------------------------------
    Description: 
There are two problems in enabling distributed scheduling.

1. If we enable the distributed scheduling only, the amrmproxy will start 
automatically and replace the token with the local one for apps in order to 
proxy any communication with rm. However, the am will still send its register 
request and allocate requests directly to real rm, and thus has invalid token.

2. If we enable both of these two settings, we would have invalid token too. 
And I don't know why.

  was:When we use distributed scheduling at nodemanager, the amrmproxy will 
replace the token of app with the local one (we suppose amrmproxy will be 
always on when we need distributed scheduling). However, if we only enable the 
distributed scheduling in yarn.xml and disable the amrmproxy, the am will 
directly connect with rm instead of amrmproxy and then lead to invalid 
amrmtoken. Thus, we should add some checks to avoid distributed scheduling 
beyond non-amrmproxy (amrmproxy and distributed scheduling are two settings 
independently in yarn.xml).


> Distributed Scheduling has invalid AMRMToken
> --------------------------------------------
>
>                 Key: MAPREDUCE-7044
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-7044
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mr-am
>    Affects Versions: 3.0.0-alpha2
>            Reporter: Jin Yibo
>            Priority: Minor
>             Fix For: 3.0.0-alpha2
>
>
> There are two problems in enabling distributed scheduling.
> 1. If we enable the distributed scheduling only, the amrmproxy will start 
> automatically and replace the token with the local one for apps in order to 
> proxy any communication with rm. However, the am will still send its register 
> request and allocate requests directly to real rm, and thus has invalid token.
> 2. If we enable both of these two settings, we would have invalid token too. 
> And I don't know why.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to