dalongliu created FLINK-12623:
---------------------------------
Summary: Flink on yarn encountered AMRMClientImpl does not update AMRM token properly
Key: FLINK-12623
URL:
https://issues.apache.org/jira/browse/FLINK-12623 Project: Flink
Issue Type: Bug
Components: Connectors / Hadoop Compatibility
Affects Versions: 1.9.0, 2.0.0
Reporter: dalongliu
Fix For: 1.9.0, 2.0.0
Hi, all! When my task running on yarn dependency flink verison is 1.7.1, I encountered the following problem:
{panel}
[org.apache.hadoop.ipc.Client ] >>> msg=Exception encountered while connecting to the server : org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.security.token.SecretManager$InvalidToken): Invalid AMRMToken from appattempt_1547520251214_0582_000001sg [2019-05-25 03:31:04.163] [WARN] [AMRM Heartbeater thread] [org.apache.hadoop.ipc.Client ] >>> msg=Exception encountered while connecting to the server : org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.security.token.SecretManager$InvalidToken): Invalid AMRMToken from appattempt_1547520251214_0582_000001sg [2019-05-25 03:31:04.168] [INFO] [AMRM Heartbeater thread] [org.apache.hadoop.yarn.client.ConfiguredRMFailoverProxyProvider] >>> msg=Failing over to rm1sg [2019-05-25 03:31:04.168] [INFO] [AMRM Heartbeater thread] [org.apache.hadoop.yarn.client.ConfiguredRMFailoverProxyProvider] >>> msg=Failing over to rm1sg [2019-05-25 03:31:30.143] [INFO] [AMRM Heartbeater thread] [org.apache.hadoop.yarn.client.ConfiguredRMFailoverProxyProvider] >>> msg=Failing over to rm2sg [2019-05-25 03:31:30.143] [INFO] [AMRM Heartbeater thread] [org.apache.hadoop.yarn.client.ConfiguredRMFailoverProxyProvider] >>> msg=Failing over to rm2sg
{panel}
Refering to the yarn issue[AMRMClientImpl does not update AMRM token properly|
https://issues.apache.org/jira/browse/YARN-3103] , I know this problem is 2.4.1 version yarn bug, this bug is fixed in 2.7.0 verison yarn. However, flink shaded hadoop version is 2.4.1, so I think this bug, flink should shade 2.7.0 version hadoop or a higher version, is my idea correct?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)