[To dev/1.3] Fix repeated RPC dispatch reusing a released FragmentInstanceContext (NPE)#18235
Merged
Conversation
|
JackieTien97
marked this pull request as ready for review
July 17, 2026 09:43
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## dev/1.3 #18235 +/- ##
==========================================
Coverage 43.78% 43.79%
Complexity 198 198
==========================================
Files 3633 3633
Lines 244245 244280 +35
Branches 29809 29812 +3
==========================================
+ Hits 106954 106979 +25
- Misses 137291 137301 +10 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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
Backport #17794 (
958ce45b13722f04bbc3837ab76caad207e15216) todev/1.3.REPEATED_RPC_CALLstatus codeIoTDBRuntimeExceptionstatus codes in both consensus-read and VirtualDataRegion pathsQueryTimeoutRuntimeExceptiontoQUERY_TIMEOUTdev/1.3 adaptation
The conflicts were resolved against the branch's existing APIs and logging style: the pre-verbose
createFragmentInstanceContextoverload and inline log messages are retained, without pulling unrelated master-only i18n or verbose-query changes into the backport.Validation
mvn clean test -pl iotdb-core/datanode -am -Dtest=RegionReadExecutorTest -Dsurefire.failIfNoSpecifiedTests=falseBUILD SUCCESSRegionReadExecutorTest: 6 tests passed, 0 failures, 0 errors