-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix boundaries on GC batch size #987
Fix boundaries on GC batch size #987
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
✅ A review job has been created and sent to the PullRequest network.
@connorgorman you can click here to see the review status or cancel the code review job.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes match the description. Should there be a test to make sure this doesn't regress?
Reviewed with ❤️ by PullRequest
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
✖️ This code review was cancelled. See Details
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR @connorgorman. Looks good to me.
@ashish-goswami Please review this PR. |
The change looks harmless. I'm merging it. |
In the value log rewrite, the check to determine if the commit was going to be within transaction limits is checked only if the value would be `>` than the max count. However, the check within the transaction is: ``` if count >= db.opt.maxBatchCount || size >= db.opt.maxBatchSize { return nil, ErrTxnTooBig } ``` (cherry picked from commit 9725af7)
In the value log rewrite, the check to determine if the commit was going to be within transaction limits only checked if the value would be
>
than the max count. However, the check within the transaction is:This change is