Repository navigation
Fail dependent tasks instead of killing the file-based scheduler thread #1081
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.
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🩺 Stability & Availability | 🟠 Major | ⚡ Quick win
Do not store a failed submission in
memory_dict. Doing so leaves duplicate futures pending forever and can block the scheduler thread.Line 188 stores an already-failed future in
memory_dict[task_key]. It does not setfile_name_dict[task_key]orcache_dir_dict[task_key]. Assume a second task with the sametask_keyreaches the queue before the next_refresh_memory_dictcall. The usual cause is two identicalsubmit()calls in a row.elif memory_dict[task_key] != task_dict["future"]branch (Line 197). Its future goes intoduplicate_dict[task_key]._refresh_memory_dictonly calls_check_task_outputfor primary futures that are not done. The primary future is already done, so it is dropped, and the code never resolves or deletes the duplicate entry. The duplicate future stays pending forever. Shutdown still returns, so the user'sresult()call hangs. Issue#1080reports this same symptom._convert_futurefinds the duplicate induplicate_dict, butk in file_name_dictis false for this key. The code then reachesreturn arg.result()(Line 408). That call blocks the scheduler thread on a future that only the scheduler thread can resolve. The whole executor deadlocks.The failed future does not need an entry in
memory_dict. Dependents of the failed future already fail through thefuture.done()check in_convert_future. If you remove Line 188, the next identical task goes through submission again and fails on its own future.🐛 Proposed fix
📝 Committable suggestion
🤖 Prompt for AI Agents