You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the above-named images (ending in either py3.11 or py3.10), Dask workers frequently fail. However, when we request workers with microarch "x86_64-v3" (as opposed to "x86_64-v2"), jobs run successfully.
This issue does not seem to happen with coffea-dask-almalinux8:v2024.5.0-py3.*.
Some details:
We are submitting jobs from a host within a container running the same image as we give to the workers. Workers access images as SIFs in CVMFS. Jobs are submitted at Wisconsin with HTCondor, through dask-jobqueue's HTCondorCluster. The only error message we see is a Dask KilledWorker exception.
The text was updated successfully, but these errors were encountered:
When using the above-named images (ending in either py3.11 or py3.10), Dask workers frequently fail. However, when we request workers with microarch "x86_64-v3" (as opposed to "x86_64-v2"), jobs run successfully.
This issue does not seem to happen with coffea-dask-almalinux8:v2024.5.0-py3.*.
Some details:
We are submitting jobs from a host within a container running the same image as we give to the workers. Workers access images as SIFs in CVMFS. Jobs are submitted at Wisconsin with HTCondor, through
dask-jobqueue'sHTCondorCluster. The only error message we see is a DaskKilledWorkerexception.The text was updated successfully, but these errors were encountered: