Repository navigation
Fix delayed operator memory release after fragment termination - #19166
Merged
Merged
Conversation
* Fix delayed fragment memory release * Fix final listener delivery when notifications are rejected (cherry picked from commit 23e1740)
|
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.
Summary
Fragment instances returned operator-memory estimates through asynchronous state listeners. When driver cleanup delayed those notifications, consecutive fast failures could hold reservations long enough to trigger false memory-insufficient errors.
Backport of Apache IoTDB #18387 (
23e1740ee07e77b4ac2cae54def7bbaac98bdfb3) todev/1.3, adapted to its state machine and operator-memory accounting.Verification
mvn spotless:apply -P with-integration-tests -pl iotdb-core/datanodepassed.