Skip to content

Conversation

@fjetter
Copy link
Member

@fjetter fjetter commented Nov 18, 2021

That's another deadlock which has been bugged the latest releases.

This does not address any dropped messages of the worker (see #5457) but avoids the exception entirely.

Apologies for the test. That level of mocking in combination with sync primitives is a big red flag but the current architecture around gather_dep does require this level of control. I believe I wrote some utils methods around this already and will look into simplifying this a bit

@fjetter fjetter mentioned this pull request Nov 18, 2021
@jrbourbeau jrbourbeau mentioned this pull request Nov 18, 2021
3 tasks
Copy link
Member

@jrbourbeau jrbourbeau left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Offline @fjetter mentioned he is confident in the changes here and would be good to include them in the upcoming release (xref dask/community#206). To that end, I'm planning to merge this PR in a bit if there are no further comments

@jrbourbeau jrbourbeau changed the title Deadlock keyerror Resolve KeyError-related deadlock Nov 18, 2021
@jrbourbeau jrbourbeau merged commit 03647c7 into dask:main Nov 18, 2021
@fjetter fjetter deleted the deadlock_keyerror branch November 19, 2021 11:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

KeyError in Worker.handle_compute_task (causes deadlock)

2 participants