-
Notifications
You must be signed in to change notification settings - Fork 28.9k
[SPARK-18762][WEBUI] Web UI should be http:4040 instead of https:4040 #16190
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Test build #69781 has started for PR 16190 at commit |
|
I think the jira number should be SPARK-18762, instead of SPARK-18761. |
|
@viirya Thanks! I've fixed it. |
|
cc: @mengxr |
|
Also, Spark Shell says as follows. |
|
Test build #69790 has finished for PR 16190 at commit
|
|
@mengxr that change is actually incorrect and shouldn't have been merged. (The test changes in the same patch are ok though.) This one LGTM. |
|
merging to master / 2.1 |
|
Hmm, looks like the original change is in branch-2.0 also, let me try to merge there too. |
## What changes were proposed in this pull request? When SSL is enabled, the Spark shell shows: ``` Spark context Web UI available at https://192.168.99.1:4040 ``` This is wrong because 4040 is http, not https. It redirects to the https port. More importantly, this introduces several broken links in the UI. For example, in the master UI, the worker link is https:8081 instead of http:8081 or https:8481. CC: mengxr liancheng I manually tested accessing by accessing MasterPage, WorkerPage and HistoryServer with SSL enabled. Author: sarutak <[email protected]> Closes #16190 from sarutak/SPARK-18761. (cherry picked from commit bb94f61) Signed-off-by: Marcelo Vanzin <[email protected]>
|
Merged to 2.0 also. |
## What changes were proposed in this pull request? When SSL is enabled, the Spark shell shows: ``` Spark context Web UI available at https://192.168.99.1:4040 ``` This is wrong because 4040 is http, not https. It redirects to the https port. More importantly, this introduces several broken links in the UI. For example, in the master UI, the worker link is https:8081 instead of http:8081 or https:8481. CC: mengxr liancheng I manually tested accessing by accessing MasterPage, WorkerPage and HistoryServer with SSL enabled. Author: sarutak <[email protected]> Closes #16190 from sarutak/SPARK-18761. (cherry picked from commit bb94f61) Signed-off-by: Marcelo Vanzin <[email protected]>
|
@sarutak Thanks for the quick fix! |
## What changes were proposed in this pull request? When SSL is enabled, the Spark shell shows: ``` Spark context Web UI available at https://192.168.99.1:4040 ``` This is wrong because 4040 is http, not https. It redirects to the https port. More importantly, this introduces several broken links in the UI. For example, in the master UI, the worker link is https:8081 instead of http:8081 or https:8481. CC: mengxr liancheng I manually tested accessing by accessing MasterPage, WorkerPage and HistoryServer with SSL enabled. Author: sarutak <[email protected]> Closes apache#16190 from sarutak/SPARK-18761.
## What changes were proposed in this pull request? When SSL is enabled, the Spark shell shows: ``` Spark context Web UI available at https://192.168.99.1:4040 ``` This is wrong because 4040 is http, not https. It redirects to the https port. More importantly, this introduces several broken links in the UI. For example, in the master UI, the worker link is https:8081 instead of http:8081 or https:8481. CC: mengxr liancheng I manually tested accessing by accessing MasterPage, WorkerPage and HistoryServer with SSL enabled. Author: sarutak <[email protected]> Closes apache#16190 from sarutak/SPARK-18761.



What changes were proposed in this pull request?
When SSL is enabled, the Spark shell shows:
This is wrong because 4040 is http, not https. It redirects to the https port.
More importantly, this introduces several broken links in the UI. For example, in the master UI, the worker link is https:8081 instead of http:8081 or https:8481.
CC: @mengxr @liancheng
I manually tested accessing by accessing MasterPage, WorkerPage and HistoryServer with SSL enabled.