event: account for raw rows in batch DML event size (#5960) - #5978
event: account for raw rows in batch DML event size (#5960)#5978ti-chi-bot wants to merge 1 commit into
Conversation
Remote batch DML events retain their row payload in RawRows until the event collector handles them. Include that payload in GetSize so dynamic stream memory and byte batching account for it.
|
This cherry pick PR is for a release branch and has not yet been approved by triage owners. To merge this cherry pick:
DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: wlwilliamx The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/test all |
This is an automated cherry-pick of #5960
What problem does this PR solve?
Issue Number: close #5959
Remote
BatchDMLEventinstances keep their encoded row payload inRawRowsuntil the event collector calls
AssembleRows.GetSizeonly accounted forRows, so dynamic stream memory control and byte-based batching treated theremote row payload as zero bytes.
What is changed and how it works?
Make
BatchDMLEvent.GetSizereturn the encodedRawRowslength before rowsare assembled. After assembly, it continues to return the decoded chunk's
memory usage.
Extend the existing remote-row assembly unit test to verify size accounting
before serialization, after remote deserialization, and after row assembly.
Check List
Tests
Questions
Will it cause performance regression or break compatibility?
No compatibility impact. Remote batches may be split earlier when their actual
payload reaches the configured byte threshold, which is the intended behavior.
Do you need to update user documentation, design documentation or monitoring documentation?
No.
Release note
Summary by CodeRabbit