[
https://issues.apache.org/jira/browse/IMPALA-11827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Rawat resolved IMPALA-11827.
-------------------------------------
Fix Version/s: Impala 4.3.0
Resolution: Fixed
> do not cache admission control service's IP address in coordinator
> ------------------------------------------------------------------
>
> Key: IMPALA-11827
> URL: https://issues.apache.org/jira/browse/IMPALA-11827
> Project: IMPALA
> Issue Type: Task
> Reporter: Abhishek Rawat
> Assignee: Abhishek Rawat
> Priority: Major
> Fix For: Impala 4.3.0
>
>
> The Impalad's ExecEnv caches resolved IP address for admission control
> service:
> [https://github.com/apache/impala/blob/master/be/src/runtime/exec-env.h#L301]
> The Impala server runs a heart beat thread for admission control service and
> it relies on the cached resolved address in ExecEnv:
> [https://github.com/apache/impala/blob/master/be/src/service/impala-server.cc#L584]
> This breaks when IP address for admission control services changes and so we
> shouldn't cache dynamic addresses.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
