You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues-all@impala.apache.org by "Abhishek Rawat (Jira)" <ji...@apache.org> on 2023/01/05 17:47:00 UTC

[jira] [Assigned] (IMPALA-11827) do not cache admission control service's IP address in coordinator

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

Abhishek Rawat reassigned IMPALA-11827:
---------------------------------------

    Assignee: Abhishek Rawat

> 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
>
> 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 run a heart beat thread for admission control service and it relies on the cached resolved address in ExecEnv. This breaks when IP address for admission control services changes (post a restart) and so we shouldn't cache dynamic addresses.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org