Subject: EXT :Re: Taskmanagers in Docker Fail to Resolve Own Hostnames and
Won't Accept Tasks
Hi Martin,
Could you `docker exec` into the problematic taskmanager and check whether the
hostname could
be resolved to a correct ip? You could use `nslookup {tm_hostname}` to verify.
Best,
Hi Martin,
Could you `docker exec` into the problematic taskmanager and check whether
the hostname could
be resolved to a correct ip? You could use `nslookup {tm_hostname}` to
verify.
Best,
Yang
Martin, Nick J [US] (IS) 于2019年12月21日周六 上午6:07写道：
> I’m running Flink 1.7.2 in a Docker swarm. Int
I'm running Flink 1.7.2 in a Docker swarm. Intermittently, new task managers
will fail to resolve their own host names when starting up. In the log I see
"no hostname could be resolved" messages coming from TaskManagerLocation. The
webUI on the jobmanager shows the taskmanagers as are associated
