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 "Tim Armstrong (Jira)" <ji...@apache.org> on 2020/06/26 19:47:00 UTC
[jira] [Resolved] (IMPALA-9790) Dockerized daemons should set
--hostname to the resolved IP
[ https://issues.apache.org/jira/browse/IMPALA-9790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Armstrong resolved IMPALA-9790.
-----------------------------------
Fix Version/s: Impala 4.0
Resolution: Fixed
> Dockerized daemons should set --hostname to the resolved IP
> -----------------------------------------------------------
>
> Key: IMPALA-9790
> URL: https://issues.apache.org/jira/browse/IMPALA-9790
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
> Reporter: Tim Armstrong
> Assignee: Tim Armstrong
> Priority: Major
> Fix For: Impala 4.0
>
>
> In light of IMPALA-9788 (and also IMPALA-9026), it probably makes the most sense to avoid using hostnames for internal communication in containerized setups, since container orchestration frameworks tend to do non-trivial things with DNS and hostnames.
> We can do this in the entrypoint script. I tried --hostname=$(hostname -I) and it seemed to work. It might need some improvement to handle cases when there are multiple IPs, etc.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org