[ https://issues.apache.org/jira/browse/YARN-10841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shilun Fan updated YARN-10841: ------------------------------ Component/s: federation Hadoop Flags: Reviewed Target Version/s: 3.4.0 Affects Version/s: 3.4.0 > Fix token reset synchronization for UAM response token > ------------------------------------------------------ > > Key: YARN-10841 > URL: https://issues.apache.org/jira/browse/YARN-10841 > Project: Hadoop YARN > Issue Type: Sub-task > Components: federation > Affects Versions: 3.4.0 > Reporter: Minni Mittal > Assignee: Minni Mittal > Priority: Minor > Labels: pull-request-available > Fix For: 3.4.0 > > Attachments: YARN-10841.v1.patch > > Time Spent: 20m > 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.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org