net: fix packet sequence when sequence overflows #378
Merged
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.
What problem does this PR solve?
Issue Number: close #377
Problem Summary:
SetSequence()
mistakenly set both the compressed and uncompressed sequences to 0.What is changed and how it works:
BeginRW
fromcompressedReadWriter
toPacketIO
so that the uncompressed sequence can be set before writing the uncompressed packet.ResetSequence()
and only set the compressed sequence to 0 when a new command begins.Check List
Tests
Tested with jdbc-test:
ConnectionRegressionTest#testBug11237
ConnectionTest#testCompression
ConnectionTest#testUseCompress
Test with sysbench (
--range_size=1000
):Notable changes
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.