Run dashboard on non-standard port and set dashboard link #25
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It looks like when running Ray clusters on Databricks there is a way to access the dashboard.
https://docs.databricks.com/en/machine-learning/ray-integration.html
It seems that on Databricks you can proxy arbitrary ports via
/driver-proxy/o/{orgId}/{clusterId}/{port}/
. But when we try it with the Dask dashboard we see a403
error.This PR starts the dashboard on a few additional ports, includingIt looks like Databricks just blocks8265
which is used by Ray's dashboard to see if8787
is being explicitly blocked.8787
for some reason, so this PR starts the Dask dashboard on8087
too in case users want to run both Dask and Ray on the same cluster.Also, set the
dashboard_link
to the correct URL.Closes #2