Repository navigation
[To dev/1.3] Fix active LOAD worker retirement leaving files pending - #19091
Merged
Merged
Conversation
(cherry picked from commit 1b2158f)
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Backport of Apache IoTDB commit
1b2158fec358ed9952f5cbca2bc1387dd46b3419.The active LOAD scheduler could retire its last worker while another file entered the pending queue, leaving that file pending. The change tracks submitted loader tasks under the executor lock and rechecks the pending queue when a worker exits.
The regression tests are adapted to the dev/1.3 deletion metadata, TsFile writer, and load-trigger APIs.
Validation:
ActiveLoadTsFileLoaderTest: 7 tests passed in both configured Surefire executions.IoTDBLoadTsFileActiveScanIT: 2 tests, 0 failures, 0 errors, 0 skipped.git diff --check: passed.