[fix][test] Fix testLargeMessage
doesn't respect the parameter clientSizeMaxMessageSize
#18452
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.
Motivation
#14382 introduced the client-side maxMessageSize for the message chunking. But the parameter
clientSizeMaxMessageSize
intestLargeMessage
is not respected in that PR. This PR fixes this issue.Modifications
clientSizeMaxMessageSize
. TheclientSizeMaxMessageSize
should not be too small because [PIP-132] Include message header size when check maxMessageSize for non-batch message on the client side. #14007 has included the metadata when calculating the chunk size.Verifying this change
This change is already covered by existing tests, such as testLargeMessage.
Does this pull request potentially affect one of the following parts:
If the box was checked, please highlight the changes
Documentation
doc
doc-required
doc-not-needed
doc-complete
Matching PR in forked repository
PR in forked repository: RobertIndie#8