[ 
https://issues.apache.org/jira/browse/FLINK-21472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17297146#comment-17297146
 ] 

Peng Zhang edited comment on FLINK-21472 at 3/8/21, 8:34 AM:
-------------------------------------------------------------

[~fly_in_gis] [~hayden zhou]  we tried with Flink 1.12.2 and got the same 
error. The error happened when a JobManager is restarted, and the new 
JobManager got the exception when trying to restore from previous state. This 
is a blocking issue in deploying Flink 1.12.1 or Flink 1.12.2 on K8S HA mode. 
So, any help is appreciated! Thanks!

BTW, we tried Flink 1.12.0 and did not have this error. So, seems this issue is 
introduced in Flink 1.12.1. However, Flink 1.12.0 has another issue 
https://issues.apache.org/jira/browse/FLINK-20648


was (Author: petrizhang):
[~fly_in_gis] [~hayden zhou]  we tried with Flink 1.12.2 and got the same 
error. The error happened when a JobManager is restarted, and the new 
JobManager got the exception when trying to restore from previous state. This 
is a blocking issue in deploying Flink 1.12.x on K8S HA mode. So, any help is 
appreciated! Thanks!

> 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)

Reply via email to