[
https://issues.apache.org/jira/browse/IMPALA-8917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Armstrong updated IMPALA-8917:
----------------------------------
Description:
I've run into multiple cases that got broken by IMPALA-8897. The general
problem is the assumption that the hostname that the Impala server refers to
itself is resolvable by the client accessing the web UI. Cases I've run into:
* In docker and kubernetes, where the internal hostnames aren't visible outside
of the internal network
* On systems without a DNS-resolvable hostname, e.g. my Ubuntu desktop that I
access via a static IP
I'm not sure what a fix would look like, but I think we at least need some way
to work around the problem in situations like this.
was:
I've run into multiple cases that got broken by IMPALA-8897. The general
problem is the assumption that the hostname that the Impala server refers to
itself is resolvable by the client accessing the web UI. Cases I've run into:
* In docker and kubernetes, where the internal hostnames aren't visible outside
of the internal network
* On systems without a DNS-resolvable hostname, e.g. my Ubuntu desktop that I
access via a static IP
> Including hostnames in debug UI URLs breaks a lot of use cases
> --------------------------------------------------------------
>
> Key: IMPALA-8917
> URL: https://issues.apache.org/jira/browse/IMPALA-8917
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
> Affects Versions: Impala 3.4.0
> Reporter: Tim Armstrong
> Assignee: Thomas Tauber-Marshall
> Priority: Blocker
>
> I've run into multiple cases that got broken by IMPALA-8897. The general
> problem is the assumption that the hostname that the Impala server refers to
> itself is resolvable by the client accessing the web UI. Cases I've run into:
> * In docker and kubernetes, where the internal hostnames aren't visible
> outside of the internal network
> * On systems without a DNS-resolvable hostname, e.g. my Ubuntu desktop that I
> access via a static IP
> I'm not sure what a fix would look like, but I think we at least need some
> way to work around the problem in situations like this.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
