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.

Issue with Dask Distributed

See original GitHub issue

Hi,

I’m having an issue with Dask Distributed. I’m running Python 3.8.10. When I run the following code, I have no issues.

from dask import dataframe as dd from dask.diagnostics import ProgressBar data1 = dd.read_csv('data1.csv') data2 = dd.read_csv('data2.csv') data = dd.concat([data1, data2], ignore_index = True).compute()

However, if I try to open a client before running the above code by using the following code from dask.distributed import Client; client = Client(); client I get the following error: AttributeError: ‘HighLevelGraph’ object has no attribute ‘dask_distributed_pack’.

Any ideas here?

Thanks!

Issue Analytics

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

Top GitHub Comments

1reaction

timhdesilvacommented, May 24, 2021

Great, thank you for all your help!

0reactions

jrbourbeaucommented, May 24, 2021

Closing as the original AttributeError has been resolved. Let us know if you run into other issues @timhdesilva

Top Results From Across the Web

Why did my worker die? - Dask.distributed

KilledWorker : this means that a particular task was tried on a worker, and it died, and then the same task was sent...

Frequently Asked Questions - Dask.distributed

Does Dask handle Data Locality?¶. Yes, both data locality in memory and data locality on disk. Often it's much cheaper to move computations...

Resilience — Dask.distributed 2022.12.0 documentation

Software fails, Hardware fails, network connections fail, user code fails. This document describes how dask.distributed responds in the face of these failures ...

Managing Memory — Dask.distributed 2022.12.1 documentation

Dask.distributed stores the results of tasks in the distributed memory of the worker nodes. The central scheduler tracks all data on the cluster...

Diagnosing Performance - Dask.distributed

... is no central place to collect data to identify performance issues. Fortunately, Dask collects a variety of diagnostic information during execution.