New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Logs are missing in frontend when dask-scheduler is restarted #2787

Closed

sanderegg opened this issue Feb 3, 2022 · 0 comments · Fixed by #2788

Assignees

Labels

bug

Member

sanderegg commented Feb 3, 2022

After the dask-scheduler is restarted the following happens in the director-v2:

if the disconnection is fast (<30seconds or so), the dask client reconnects BUT:

all the Pub/Sub linked to the previous scheduler are NOT updated for the new scheduler
--> No logging/progress/state updates are flowing to the director-v2 anymore

If the disconnection is slow, the problem is recognized as sending a task triggers an Exception in dask code.
The dask-workers are supposed to reconnect and until now they seem to do so

sanderegg added the bug label

sanderegg self-assigned this

sanderegg mentioned this issue

🐛 Check dask scheduler ID in cluster, if it changes raise an exception #2788

Merged

sanderegg closed this as completed in #2788

sanderegg added this to the R.Schumann milestone

sanderegg mentioned this issue

maintenance/scaling of the platform ITISFoundation/osparc-issues#428

Closed

2 tasks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment