We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I have been noticing very long wait times to get dask workers to come online lately.
It just took me ~30 min to get any workers on the pangeo google cloud deployment.
Is there a way to resolve this? @rabernat suggested that "the cluster is maxed out".
For completeness, this is what I do in my notebook (pretty much the recommmended code):
from dask_gateway import GatewayCluster cluster = GatewayCluster() # cluster.adapt(minimum=4, maximum=40) # or to a fixed size. cluster.scale(10) cluster
The text was updated successfully, but these errors were encountered:
Apparently we have a 100 vCPU limit on the cluster, and today we were at that limit.
I just bumped it to 200. (For those with access, the page is here: https://console.cloud.google.com/kubernetes/clusters/details/us-central1-b/pangeo-uscentral1b/details?project=pangeo-181919)
Did that resolve the issue?
Sorry, something went wrong.
I was eventually able to get workers even before raising this issue, but Ill keep an eye out in the upcoming days.
Quick update: Right now I am getting dask workers quickly! Thanks for the adjustment.
No branches or pull requests
I have been noticing very long wait times to get dask workers to come online lately.
It just took me ~30 min to get any workers on the pangeo google cloud deployment.
Is there a way to resolve this? @rabernat suggested that "the cluster is maxed out".
For completeness, this is what I do in my notebook (pretty much the recommmended code):
The text was updated successfully, but these errors were encountered: