Closed exalate-issue-sync[bot] closed 1 year ago
Eric Gudgion commented: This seems to work:
sparkling-shell --conf "spark.driver.extraJavaOptions=-Dai.h2o.form_auth" --conf "spark.driver.extraJavaOptions=-Dai.h2o.hash_login" --conf "spark.ext.h2o.login.conf=/tmp/dummy"
Maybe document or record it for the future as a way to disable the webUI.
Jakub Hava commented: Thanks [~accountid:5a132830cba5b30325a6d0ee] for investigation. I tried it myself as well. We don't even need to set up form_auth
Also, these configuration can be already specified as using Sparkling Water configuration as:
sparkling-shell --conf "spark.ext.h2o.hash.login=true" --conf "spark.ext.h2o.login.conf=/tmp/dummy"
Jakub Hava commented: We we have 2 choices:
Either document that sparkling-shell --conf "spark.ext.h2o.hash.login=true" --conf "spark.ext.h2o.login.conf=/tmp/dummy"
can be used to disable the flow UI
Or I can create a new configuration called spark.ext.h2o.client.disable.web
which will internally create dummy login conf and set the required parameters to achieve the same result.
I'm voting for the later option as it's easier for the user as it's just one, explicit option. What do you think [~accountid:5a132830cba5b30325a6d0ee]?
Jakub Hava commented: Created PR https://github.com/h2oai/sparkling-water/pull/877 where we need to do just
./bin/sparkling-shell --conf "spark.ext.h2o.client.enable.web=false"
JIRA Issue Migration Info
Jira Issue: SW-977 Assignee: Jakub Hava Reporter: Eric Gudgion State: Resolved Fix Version: 2.1.36 Attachments: N/A Development PRs: Available
Linked PRs from JIRA
JIRA Issue Migration Info Cont'd
Jira Issue Created Date: 2018-08-06T14:05:30.908-0700
For environments that do not want to use the Flow UI from Spark, the interface cannot be disabled using --conf "client.web.enable=false"
Using --conf "spark.driver.extraJavaOptions=-Dai.h2o.disable_web" as a workaround works, but pysparkling and rsparkling will not work, which is a large downside.