[jira] [Closed] (FLINK-19677) TaskManager takes abnormally long time to register with JobManager on Kubernetes

["Till Rohrmann (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-19677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Till Rohrmann closed FLINK-19677.
---------------------------------
    Resolution: Fixed

Fixed via

1.12.0: 8fd36be35c4cff31960de6478295742952c93d55
1.11.3: d251ce5ab43d89d3d09a3f09ecf9a33435e5d901

> TaskManager takes abnormally long time to register with JobManager on Kubernetes
> --------------------------------------------------------------------------------
>
>                 Key: FLINK-19677
>                 URL: https://issues.apache.org/jira/browse/FLINK-19677
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Task
>    Affects Versions: 1.11.0, 1.11.1, 1.11.2
>            Reporter: Weike Dong
>            Assignee: Weike Dong
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.12.0, 1.11.3
>
>
> During the registration process of TaskManager, JobManager would create a 
> _TaskManagerLocation_ instance, which tries to get hostname of the TaskManager via reverse DNS lookup.
> However, this always fails in Kubernetes environment, because for pods that are not exposed by Services, their IPs cannot be resolved to domains by coredns, and _InetAddress#getCanonicalHostName()_ would take ~5 seconds to return, blocking the whole registration process.
> Therefore Flink should provide a configuration parameter to turn off reverse DNS lookup. Also, even when hostname is actually needed, this could be done lazily to avoid blocking registration of other TaskManagers.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)