[
https://issues.apache.org/jira/browse/YARN-10841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bibin Chundatt reassigned YARN-10841:
-------------------------------------
Assignee: Bibin Chundatt (was: Minni Mittal)
> Fix token reset synchronization by making sure for UAM response token reset
> is done while in lock.
> ---------------------------------------------------------------------------------------------------
>
> Key: YARN-10841
> URL: https://issues.apache.org/jira/browse/YARN-10841
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Minni Mittal
> Assignee: Bibin Chundatt
> Priority: Minor
> Labels: pull-request-available
> Attachments: YARN-10841.v1.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> *2021-06-24T10:11:39,465* [ERROR] [AMRM Heartbeater thread]
> |impl.AMRMClientAsyncImpl|: Exception on heartbeat
> org.apache.hadoop.yarn.exceptions.YarnException:
> org.apache.hadoop.yarn.exceptions.YarnRuntimeException: amrmToken from UAM
> cluster-0 should be null here
> at
> org.apache.hadoop.yarn.server.nodemanager.amrmproxy.FederationInterceptor.allocate(FederationInterceptor.java:782)
>
>
> *2021-06-24T10:10:12,608* INFO [616916] FederationInterceptor: Received new
> UAM amrmToken with keyId 843616604
> Hearbeatcallback sets token to null. But because of synchroniztion issue, it
> happened after mergeAllocate is called. So, while allocate merge is happening
> the value should get set to null and should have happened Inside lock
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
