question-mark
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.

WARNING - Memory use is high but worker has no data to store to disk

See original GitHub issue

I end up getting a lot of error messages like this:

distributed.worker - WARNING - Memory use is high but worker has no data to store to disk.  Perhaps some other process is leaking memory?  Process memory: 6.15 GB -- Worker memory limit: 8.45 GB

I’m relatively sure that this warning is actually true. Also, the workers hitting this warning end up in idling all the time.

Is there a way to automatically retire + restart the workers that hit this error message?

Anything else we need to know?: I’m using Dask v2.30

Environment:

  • Dask version: v2.30
  • Python version: 3.7.8
  • Operating System: Centos 7
  • Install method (conda, pip, source): conda

Issue Analytics

  • State:open
  • Created 3 years ago
  • Reactions:1
  • Comments:17 (7 by maintainers)

github_iconTop GitHub Comments

1reaction
Hoezecommented, Nov 10, 2020

@KrishanBhasin I am currently running with a fork of d7f532caa1564ef09d456d60125c03200fa60fef (see #4221). So, yes, I am already using the fixes from 2.30.1, but they do not seem to solve the issue.

The workers still keep freezing and I cannot get my calculations to finish.

1reaction
mrocklincommented, Oct 31, 2020

The testing infrastructure is pretty good for this, especially if you can write async code: https://distributed.dask.org/en/latest/develop.html#writing-tests

Dask can run itself entirely in one thread, which really helps with debugging.

On Sat, Oct 31, 2020 at 11:59 AM Florian R. Hölzlwimmer < notifications@github.com> wrote:

OK sure. I’m happy to debug 😃 Nonetheless if you have tips how to get dask workers into debug mode (with pycharm) I’d be even more happy 😄

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/dask/distributed/issues/4193#issuecomment-719973852, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACKZTHXTTLIXQJJJP63MGLSNRM7XANCNFSM4TBKFTIQ .

Read more comments on GitHub >

github_iconTop Results From Across the Web

distributed.worker Memory use is high but worker has no ...
That warning is saying that your process is taking up much more memory than you are saying is OK. In this situation Dask...
Read more >
Tackling unmanaged memory with Dask
Shed light on the common error message “Memory use is high but worker has no data to store to disk. Perhaps some other...
Read more >
Worker Memory Management
In many cases, high unmanaged memory usage or “memory leak” warnings on workers can be misleading: a worker may not actually be using...
Read more >
Dask Unmanaged Memory | How to Find & Fix | Matt Rocklin
Learn more at https://bit.ly/3Q5aMmpUnmanaged memory often presents as a memory leak, but is actually really easy to identify and resolve.
Read more >
Understanding Performance
MiniAn heavily use the dask package to carry out all computations in parallel. ... like “memory usage is high but no data to...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found