[
https://issues.apache.org/jira/browse/FLINK-21472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17297229#comment-17297229
]
Yang Wang commented on FLINK-21472:
-----------------------------------
I have tested in my minikube. After setting the jobmanager rpc address to pod
IP, the {{FencingTokenException}} will disappear. I think we should update the
documentation to suggest our users to use pod IP instead of Kubernetes service
when HA enabled.
> 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)
