flink-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From John Stone <elliotst...@gmail.com>
Subject Re: TaskManagers cannot contact JobManager in Kubernetes when JobManager HA is enabled
Date Thu, 01 Nov 2018 15:22:46 GMT
I've managed to resolve the issue.  With HA enabled, you will see this message in the logs:

2018-11-01 13:38:52,467 INFO  org.apache.flink.runtime.entrypoint.ClusterEntrypoint      
  - Actor system started at akka.tcp://flink@flink-jobmanager:40641

Without HA enabled, you will see this message in the logs:

2018-11-01 13:38:52,467 INFO  org.apache.flink.runtime.entrypoint.ClusterEntrypoint      
  - Actor system started at akka.tcp://flink@flink-jobmanager:6123

HA causes a random port assignment for the ResourceManager portion of the JobManager.  This
can be controlled by setting the high-availability.jobmanager.port to a fixed port and exposing
it in the Kubernetes network configuration.

Mime
View raw message