Ensure checkpoint tasks complete on IO exceptions #15089
Merged
+30
−21
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.
I was investigating the following crash where a checkpoint task had its underlying resources being destroyed while it was still running. The two interesting threads are the following:
The problem is that if there's an IO exception being thrown in
RowGroupCollection::Checkpoint
after some (but not all) checkpoint tasks have been scheduled but beforecheckpoint_state.executor.WorkOnTasks();
is called, it results in an InternalException / DuckDB crash as theCheckpoint
method does not wait for the scheduled tasks to have completed before destroying the referenced resources.