Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[BUG] dask-cuda(0.7.0) is broken with latest distributed(2.0.1)

See original GitHub issue

dask-cuda is not compatible with latest distributed

Log:-

(base) builder@5ab0d442c86f:~$ dask-cuda-worker
Traceback (most recent call last):
  File "/opt/anaconda3/bin/dask-cuda-worker", line 11, in <module>
    load_entry_point('dask-cuda==0.7.0', 'console_scripts', 'dask-cuda-worker')()
  File "/opt/anaconda3/lib/python3.6/site-packages/pkg_resources/__init__.py", line 489, in load_entry_point
    return get_distribution(dist).load_entry_point(group, name)
  File "/opt/anaconda3/lib/python3.6/site-packages/pkg_resources/__init__.py", line 2843, in load_entry_point
    return ep.load()
  File "/opt/anaconda3/lib/python3.6/site-packages/pkg_resources/__init__.py", line 2434, in load
    return self.resolve()
  File "/opt/anaconda3/lib/python3.6/site-packages/pkg_resources/__init__.py", line 2440, in resolve
    module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/opt/anaconda3/lib/python3.6/site-packages/dask_cuda/dask_cuda_worker.py", line 12, in <module>
    from distributed.worker import _ncores
ImportError: cannot import name '_ncores'
(base) builder@5ab0d442c86f:~$

Conda package :-

(base) builder@5ab0d442c86f:~$ conda list | grep distributed
distributed               2.0.1                      py_0
(base) builder@5ab0d442c86f:~$

(base) builder@5ab0d442c86f:~$ conda list | grep dask
dask                      2.0.0                      py_0
dask-core                 2.0.0                      py_0
dask-cuda                 0.7.0           py36_489.g8bce79e    
dask-cudf                 0.9.0a          py36_493.g2167909    
(base) builder@5ab0d442c86f:~$

Issue Analytics

State:
Created 4 years ago
Comments:15 (7 by maintainers)

Top GitHub Comments

1reaction

pentschevcommented, Jan 9, 2020

Since this is related to an older version of dask-cuda which isn’t supported anymore I’m closing this issue. If anything similar happens to an up-to-date version, please feel free to file a new issue.

1reaction

pentschevcommented, Aug 13, 2019

@ChethanUK can you ensure the machine where the traceback came from is actually running dask-cuda 0.8? I think that is from 0.7, the import _ncores was removed is 0.8. If you’re running a cluster, it could be that the node running the worker has a different version than the one where you pasted conda list from.

Top Results From Across the Web

Dask-cuda-worker not registering with scheduler - Distributed

When I create a cluster with a pod template that requests a GPU, however, the nodes are created but they don't register with...

Bug listing with status RESOLVED with resolution OBSOLETE ...

Bug :1523 - "[IDEA] Offload work by distributing trivial ebuild maintenance to users, introduce a simple stability voting system and have a core...

Python on Biowulf

User environments that were using symbolic links to the central package cache likely were broken during the transition and will have to be...

AutoGluon for tabular playground oct 2021

Successfully installed scikit-learn-1.0 WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system ...

SQL Server 2019 Big Data Clusters CU17 release notes

Library Version Library Version Library Version _libgcc_mutex 0.1 keras‑applications 1.0.8 python 3.8.10 _openmp_mutex 4.5 keras‑preprocessing 1.1.2 pytorch 1.8.1 _py‑xgboost‑mutex 2 keras2onnx 1.6.5 pyqt 5.12.3