You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I started a new cluster hosted on http://127.0.01/:33459 using the +NEW button, and it appropriately shows the many options for managing/monitoring the cluster. If I try to search for http://127.0.0.1/33459 using the search bar at the top, nothing comes up. It instead connects to dask/dashboard/511c94dc-3b49-4f8b-95be-f30f959a41aa. Is there some network proxy I should be aware of?
Also, as a side-note question, can dask_cuda.LocalCUDACluster be used to integrate GPUs in the cluster when the module is added to the .yml file for cluster customization?
The text was updated successfully, but these errors were encountered:
@samanake It looks like you have typos in your URLs. The URL needs to be http://<host>:<port>, in this case http://127.0.0.1:33459 (you need the :, and it shouldn't have / before it). Does that help?
I started a new cluster hosted on http://127.0.01/:33459 using the +NEW button, and it appropriately shows the many options for managing/monitoring the cluster. If I try to search for
http://127.0.0.1/33459
using the search bar at the top, nothing comes up. It instead connects todask/dashboard/511c94dc-3b49-4f8b-95be-f30f959a41aa
. Is there some network proxy I should be aware of?Also, as a side-note question, can
dask_cuda.LocalCUDACluster
be used to integrate GPUs in the cluster when the module is added to the .yml file for cluster customization?The text was updated successfully, but these errors were encountered: