Intermittent `distributed.utils - ERROR - 'cpu'`
See original GitHub issueI just upgraded to the latest distributed/dask versions, and I am getting this intermittent keyError that’s difficult to characterize precisely and debug. I was wondering if anyone knows what’s the root cause for this issue?
distributed.utils - ERROR - 'cpu'
Traceback (most recent call last):
File "/glade/work/abanihi/softwares/miniconda3/envs/analysis/lib/python3.7/site-packages/distributed/utils.py", line 662, in log_errors
yield
File "/glade/work/abanihi/softwares/miniconda3/envs/analysis/lib/python3.7/site-packages/distributed/dashboard/scheduler.py", line 594, in update
cpu = [int(ws.metrics["cpu"]) for ws in workers]
File "/glade/work/abanihi/softwares/miniconda3/envs/analysis/lib/python3.7/site-packages/distributed/dashboard/scheduler.py", line 594, in <listcomp>
cpu = [int(ws.metrics["cpu"]) for ws in workers]
KeyError: 'cpu'
distributed.utils - ERROR - 'cpu'
Traceback (most recent call last):
File "/glade/work/abanihi/softwares/miniconda3/envs/analysis/lib/python3.7/site-packages/distributed/utils.py", line 662, in log_errors
yield
File "/glade/work/abanihi/softwares/miniconda3/envs/analysis/lib/python3.7/site-packages/distributed/dashboard/scheduler.py", line 594, in update
cpu = [int(ws.metrics["cpu"]) for ws in workers]
File "/glade/work/abanihi/softwares/miniconda3/envs/analysis/lib/python3.7/site-packages/distributed/dashboard/scheduler.py", line 594, in <listcomp>
cpu = [int(ws.metrics["cpu"]) for ws in workers]
KeyError: 'cpu'
$ conda list distributed
# packages in environment at /glade/work/abanihi/softwares/miniconda3/envs/analysis:
#
# Name Version Build Channel
distributed 2.5.2 py_0 conda-forge
$ conda list dask
# packages in environment at /glade/work/abanihi/softwares/miniconda3/envs/analysis:
#
# Name Version Build Channel
dask 2.5.2 py_0 conda-forge
dask-core 2.5.2 py_0 conda-forge
dask-jobqueue 0.7.0 py_0 conda-forge
dask-mpi 2.0.0 py37_0 conda-forge
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
KeyError: ('fetch', 'memory') in Dask 2017.7.2 ... - GitHub
This indicates an inconsistency in the worker state machine where a worker is trying to do two things simultaneously for a given task,...
Read more >keep getting "distributed.utils_perf - WARNING - full garbage ...
I keep getting "distributed.utils_perf - WARNING - full garbage collections took 19% CPU time recently" warning message after I finished ...
Read more >Changelog — Dask.distributed 2022.12.1 documentation
2022.11.0¶. Released on November 15, 2022. Note. This release changes the default scheduling mode to use queuing. This will significantly reduce cluster memory ......
Read more >Troubleshoot Hardware and Common Issues on Catalyst ...
This document describes how to troubleshoot hardware and related common issues on Catalyst 6500/6000 switches that run Cisco IOS® system ...
Read more >Fix List for Db2 Version 11.5 for Linux, UNIX and Windows - IBM
DT147361 2 IT40335: HADR STANDBY IS SHUTDOWN DUE TO NOT FINDING A LOG FIL...
DT148449 2 IT40091: DB2CKBKP FAILS TO VALIDATE REMOTE BACKUP
DT147546 2...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’m taking a look now. I think I see a way where this could happen. @andersy005 does this only happen just when a worker comes online?
Thanks for following up @andersy005! Feel free to re-open if the error pops up again