[fix](query-forward) Fix forward query exception or stuck or potential query result loss (#41303) #42368
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.
Proposed changes
Fix forward query exception if no status code is set in master execution. EOF may result in this status.
Fix forward query stuck due to no result packet sent to mysql channel. Should use result packets from master.
Fix potential forward query result loss if follower can read status change during query process. Should judge by the status once before execution.
Add assertion for regression test.