[
https://issues.apache.org/jira/browse/IMPALA-4050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16934750#comment-16934750
]
ASF subversion and git services commented on IMPALA-4050:
---------------------------------------------------------
Commit 16e0d550c28a59510fb152d1d2ad32ac9dac741c in impala's branch
refs/heads/master from Thomas Tauber-Marshall
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=16e0d55 ]
IMPALA-4057, IMPALA-4050: Fix --webserver_interface
This patch fixes two issues with --webserver_interface:
- When --webserver_interface was used start-impala-cluster.py with a
value that's different from --hostname, minicluster startup would
appear to fail as liveness is determined by checking for the webui's
availability at the address specified for --hostname.
- The value of --webserver_interface was applied correctly for the
catalogd and statestored but not for impalads, due to the way
ExecEnv constructed the Webserver.
- It is now possible to specify a hostname for webserver_interface
instead of an IP. The webserver will resolve the hostname.
This patch also upgrades our version of psutil to the latest for the
function 'net_if_addrs'. This requires a few change to our use of
psutil, mostly adding '()' to call functions that previously were
variables.
Testing:
- Added a custom cluster test that finds all available interfaces,
binds the webserver to one of them, and checks that its only
available over that interface.
Change-Id: Ic7e75908426756d73f13a0fa3cfc21fc31da164c
Reviewed-on: http://gerrit.cloudera.org:8080/14266
Reviewed-by: Impala Public Jenkins <impala-public-jenk...@cloudera.com>
Tested-by: Impala Public Jenkins <impala-public-jenk...@cloudera.com>
> Support starting webserver specified by hostname
> ------------------------------------------------
>
> Key: IMPALA-4050
> URL: https://issues.apache.org/jira/browse/IMPALA-4050
> Project: IMPALA
> Issue Type: New Feature
> Components: Backend
> Affects Versions: Impala 2.7.0
> Environment: LSB Version:
> :base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch
> Distributor ID: CentOS
> Description: CentOS release 6.7 (Final)
> Release: 6.7
> Codename: Final
> Reporter: hewenting
> Assignee: hewenting
> Priority: Major
> Labels: impala, webserver
>
> Start impala service failed when add impala arguments webserver_interface
> valued by hostname.
> my command: ./bin/start-impala-cluster.py -s 1 --impalad_args
> '-webserver_interface={color:red}nobida141{color}'.
> log displayed on terminal:
> {noformat}
> MainThread: Found 1 impalad/1 statestored/1 catalogd process(es)
> MainThread: Getting num_known_live_backends from nobida141:25000
> MainThread: Debug webpage not yet available.
> MainThread: Debug webpage not yet available.
> ...
> MainThread: Debug webpage did not become available in expected time.
> MainThread: Waiting for num_known_live_backends=1. Current value: None
> Error starting cluster: num_known_live_backends did not reach expected value
> in time
> {noformat}
> log on file Impalad.INFO:
> {noformat}
> I0831 13:49:11.234997 419171 webserver.cc:365] Webserver: set_ports_option:
> nobida141:25000: invalid port spec. Expecting list of: [IP_ADDRESS:]PORT[s|r]
> I0831 13:49:11.334241 419171 status.cc:114] Webserver: Could not start on
> address nobida141:25000
> @ 0x11b4e29 impala::Status::Status()
> @ 0x15fef7f impala::Webserver::Start()
> @ 0x1348f8b impala::ExecEnv::StartServices()
> @ 0x1534a59 ImpaladMain()
> @ 0x115ec40 main
> @ 0x3f8981ed5d (unknown)
> @ 0x115ea4d (unknown)
> E0831 13:49:11.334287 419171 impalad-main.cc:87] Impalad services did not
> start correctly, exiting. Error: Webserver: Could not start on address
> nobida141:25000
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
