[
https://issues.apache.org/jira/browse/YARN-10794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17367924#comment-17367924
]
Song Jiacheng edited comment on YARN-10794 at 6/23/21, 7:33 AM:
----------------------------------------------------------------
This has been fixed by https://issues.apache.org/jira/browse/YARN-10229
Sorry for not seeing that, Closing it.
was (Author: song jiacheng):
This has been fixed by https://issues.apache.org/jira/browse/YARN-9693
Sorry for not seeing that, Closing it.
> Submitting jobs to a single subcluster will fail while AMRMProxy is enabled
> ---------------------------------------------------------------------------
>
> Key: YARN-10794
> URL: https://issues.apache.org/jira/browse/YARN-10794
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
> Affects Versions: 3.2.1
> Reporter: Song Jiacheng
> Priority: Major
> Attachments: YARN-10794.v1.patch, YARN-10794.v2.patch
>
>
> Sorry for not knowing how to quote a issue...
> https://issues.apache.org/jira/browse/YARN-9693
> This issue has already raised this problem, but it seems that I can't submit
> job by the federation client while using the patch.
> The original reason of this problem is that NM will set a local AMRMToken for
> AM if AMRMProxy is enabled, so that AM will fail if it contact with RM
> directly.
> This problem makes it impossible to rolling upgrade to federation, cause we
> can't upgrade all the NMs and clients at one moment
> So I developed another patch, using this patch I can submit jobs via the both
> ways.
> My solution is that hold two tokens at the same time, and choose a right one
> during the building of RPC Client.
> I tested this patch in some situations like AM recover, NM recover, no error
> found.
> But still, I can't ensure this patch is good, so i wonder if there is a
> better solution.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
