[
https://issues.apache.org/jira/browse/FLINK-21472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17297340#comment-17297340
]
Peng Zhang commented on FLINK-21472:
------------------------------------
[~fly_in_gis] I tried to pass IP address as `host` to start JobManager. So,
JobManger and TaskManagers can start and jobs can be running in the Flink
cluster. However, there is another issue when JobManger has some jobs running
with checkpoints, and then restarts, JobManager cannot restart with some error
{{2021-03-08 13:14:55,594 WARN akka.remote.ReliableDeliverySupervisor [] -
Association with remote system [akka.tcp://[email protected]:6123] has failed,
address is now gated for [50] ms. Reason: [Association failed with
[akka.tcp://[email protected]:6123]] Caused by:
[java.net.NoRouteToHostException: No route to host]}}
It seems that it tries to connect to previous JobManager IP address. So, could
you check this? and should I create another issue?
> FencingTokenException: Fencing token mismatch
> ---------------------------------------------
>
> Key: FLINK-21472
> URL: https://issues.apache.org/jira/browse/FLINK-21472
> Project: Flink
> Issue Type: Bug
> Components: Deployment / Kubernetes
> Affects Versions: 1.12.1
> Reporter: hayden zhou
> Priority: Major
> Attachments:
> flink--standalonesession-0-mta-flink-jobmanager-864d6c8cbb-rmsxw.log
>
>
> org.apache.flink.runtime.rest.handler.job.JobsOverviewHandler [] - Unhandled
> exception.
> org.apache.flink.runtime.rpc.exceptions.FencingTokenException: Fencing token
> mismatch: Ignoring message
> LocalFencedMessage(8fac01d8e3e3988223a2e5c6e3f04f1e,
> LocalRpcInvocation(requestMultipleJobDetails(Time))) because the fencing
> token 8fac01d8e3e3988223a2e5c6e3f04f1e did not match the expected fencing
> token 8c37414f464bca76144e6cabc946474b.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
