Hi all,
We are running some of our Flink jobs with Job Manager High Availability.
Occasionally we get a cluster that comes up improperly and doesn’t respond.
Attempts to submit the job seem to hang and when we hit the /overview REST
endpoint in the Job Manager we get a 500 error and a fencing token exception
like this:
2019-09-21 05:04:07.785 [flink-akka.actor.default-dispatcher-4428] level=ERROR
o.a.f.runtime.rest.handler.cluster.ClusterOverviewHandler - Implementation
error: Unhandled exception.
org.apache.flink.runtime.rpc.exceptions.FencingTokenException: Fencing token
not set: Ignoring message LocalFencedMessage(null,
LocalRpcInvocation(requestResourceOverview(Time))) sent to
akka.tcp://fl...@job-ef80a156-3350-4e85-8761-b0e42edc346f-jm-0.job-ef80a156-3350-4e85-8761-b0e42edc346f-jm-svc.olp-here-test-j-ef80a156-3350-4e85-8761-b0e42edc346f.svc.cluster.local:6126/user/resourcemanager
because the fencing token is null.
at
org.apache.flink.runtime.rpc.akka.FencedAkkaRpcActor.handleRpcMessage(FencedAkkaRpcActor.java:59)
at
org.apache.flink.runtime.rpc.akka.AkkaRpcActor.onReceive(AkkaRpcActor.java:142)
at
org.apache.flink.runtime.rpc.akka.FencedAkkaRpcActor.onReceive(FencedAkkaRpcActor.java:40)
at
akka.actor.UntypedActor$$anonfun$receive$1.applyOrElse(UntypedActor.scala:165)
at akka.actor.Actor$class.aroundReceive(Actor.scala:502)
at akka.actor.UntypedActor.aroundReceive(UntypedActor.scala:95)
at akka.actor.ActorCell.receiveMessage(ActorCell.scala:526)
at akka.actor.ActorCell.invoke(ActorCell.scala:495)
at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:257)
at akka.dispatch.Mailbox.run(Mailbox.scala:224)
at akka.dispatch.Mailbox.exec(Mailbox.scala:234)
at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
at
scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)
at
scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
at
scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)
We are running Flink 1.7.1 in Kubernetes and run each job in its own namespace
with a three-node Zookeeper cluster and two Job Managers, plus one or more Task
Managers. I have been able to replicate the issue, but don’t find any
difference in the logs between a failing cluster and a good one.
Does anyone here have any ideas as to what’s happening, or what I should be
looking for?
-Bruce
[cid:image001.png@01D2B473.0F7F85E0]
Bruce Hanson
Principal Engineer
M: +1 425 681 0422
HERE Technologies
701 Pike Street, Suite 2000
Seattle, WA 98101 USA
47° 36' 41" N 122° 19' 57" W
[cid:image002.png@01D2B473.0F7F85E0]<http://360.here.com/>
[cid:image003.png@01D2B473.0F7F85E0] <https://www.twitter.com/here>
[cid:image004.png@01D2B473.0F7F85E0] <https://www.facebook.com/here>
[cid:image005.png@01D2B473.0F7F85E0]
<https://www.linkedin.com/company/heremaps>
[cid:image006.png@01D2B473.0F7F85E0] <https://www.instagram.com/here/>
