[To dev/1.3] Fix IoTConsensus batch accumulation and config reload (#18501) - #18507
Merged
Conversation
Backport apache#18501 to origin/dev/1.3.
Caideyipi
changed the title
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
2 participants
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 Apache IoTDB PR #18501 and #18522 to origin/dev/1.3. This adapts hot-reloaded memory limits to the 1.3 absolute-limit API and propagates configuration changes to existing dispatcher threads. It also includes the #18522 batch accumulation latency fix, which stops waiting as soon as a batch reaches its entry limit.
Tests: mvn -pl iotdb-core/consensus -Dtest=IoTConsensusMemoryManagerTest,LogDispatcherTest -DfailIfNoTests=false test