Open gdkrmr opened 1 year ago
Try updating to latest xarray and dask. dask has had some nice updates lately, https://medium.com/pangeo/dask-distributed-and-pangeo-better-performance-for-everyone-thanks-to-science-software-63f85310a36b
This must be something to do with zarr itself.
cc @martindurant
I recommend turning on logging in the HTTP file system
client = Client(n_workers=1, threads_per_worker=32, memory_limit='64GB')
client.run(fsspec.utils.setup_logging, logger_name="fsspec.http")
fsspec.utils.setup_logging(logger_name="fsspec.http")
and looking for errors
What happened?
Under load blocks of Zarr objects go missing. This happens on our minio server (see example) and on the hpc file system. This happens under load, when the filesystem gets slow, so I guess there must be a timeout somewhere.
What did you expect to happen?
A complete map.
Incomplete map:
Complete map, when the filesystem is not under load:
Minimal Complete Verifiable Example
MVCE confirmation
Relevant log output
No response
Anything else we need to know?
This only seems to happen under load, so you will need to stress the server a bit to reproduce it.
Environment