user/dispatcher because the fencing token is null.
Forwarding messages
From: "Alex.Hu"
Date: 2019-07-01 10:17:15
To: "Yang Wang"
Cc: user
Subject: Re:Re: About "Flink 1.7.0 HA based on zookeepers "
Hi,Wang:
Thank you very much for a
la.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)
> Caused by: org.apache.flink.runtime.rpc.exceptions.FencingTokenException:
> Fencing token not set: Ignoring message
> LocalFencedMessage(98b7a69a48c04a9ca01b1eca2b714146,
> LocalRpcInvocation(requestRestAddress
62236/user/dispatcher because the fencing token is null.
Forwarding messages
From: "Alex.Hu"
Date: 2019-07-01 10:17:15
To: "Yang Wang"
Cc: user
Subject: Re:Re: About "Flink 1.7.0 HA based on zookeepers "
Hi,Wang:
Thank you very much for an
Hi,Wang:
Thank you very much for answering my question!
I hope to start multiple jobmanagers on kubernete, because according to my
understanding in the document of jobmanager_high_availability, the standalone
mode should be that the jobmanager can be replaced seamlessly when the fault
no
Hi, hu
I am not sure why do you need to start multiple jobmanagers on kubernetes.
Just as the manual [1], we use a deployment of 1 to make sure kubernetes
detect the crash of jobmanager and start a new one. What we should do is to
add the high availability configurations [2] in flink-conf.yaml. Yo
HI Tan:
I have the same problem with you when running "flink-1.7.2 ON KUBERNATE HA"
mode, may I ask if you have solved this problem? How? After I started the two
jobmanagers normally, when I tried to kill one of them, he could not restart
normally. Both jobmanagers reported this error. The speci
