-
Notifications
You must be signed in to change notification settings - Fork 709
reference/configuration: add description about TiDB txn-total-size-limit #2002
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
Conversation
|
|
||
| - The size limit of a transaction. | ||
| - Default value: `104857600` | ||
| - The total key-value entries size in bytes should be less than this value. Note, if the `binlog` is enabled, this value should be less than 104857600(100M), because of the limitation of the binlog component; If `binlog` is not enabled, the maximum value of this configuration is 10737418240(10G). |
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.
Should we set a lower limit, if the size is too low, TiDB will not start? This comment may not be related to the documentation.
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.
Not necessary. Our customers are sane enough.
| ### `txn-total-size-limit` | ||
|
|
||
| - The size limit of a transaction. | ||
| - Default value: `104857600` |
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.
What about adding a unit?
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.
In the description, it says "size in bytes" @TomShawn
|
@tiancaiamao Please address the above comments, thanks! |
Co-Authored-By: TomShawn <41534398+TomShawn@users.noreply.github.com>
TomShawn
left a comment
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.
LGTM
TomShawn
left a comment
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.
LGTM
|
PTAL @jackysp |
jackysp
left a comment
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.
LGTM
|
cherry pick to release-4.0 in PR #2181 |
What is changed, added or deleted? (Required)
Update configuration-file.go, add description about TiDB txn-total-size-limit
Which TiDB version(s) do your changes apply to? (Required)
If you select two or more versions from above, to trigger the bot to cherry-pick this PR to your desired release version branch(es), you must add corresponding labels such as needs-cherry-pick-3.1, needs-cherry-pick-3.0, and needs-cherry-pick-2.1.
What is the related PR or file link(s)?
http://github.com/pingcap/tidb/pull/14522