-
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
Not recommend setting tiflash logical split since 6.2 #10840
Not recommend setting tiflash logical split since 6.2 #10840
Conversation
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
Signed-off-by: JaySon-Huang <[email protected]>
6614511
to
5a91553
Compare
Signed-off-by: JaySon-Huang <[email protected]>
/cc @flowbehappy |
Signed-off-by: JaySon-Huang <[email protected]>
Comment addressed. PTAL again @shichun-0415 @flowbehappy |
Co-authored-by: shichun-0415 <[email protected]>
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
Co-authored-by: shichun-0415 <[email protected]>
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.
Rest LGTM
/verify |
Signed-off-by: JaySon-Huang <[email protected]>
/verify |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 710f911
|
Signed-off-by: JaySon-Huang [email protected]
First-time contributors' checklist
What is changed, added or deleted? (Required)
According to pingcap/tiflash#5576, if user deploys tiflash with explicit setting
profiles.default.dt_enable_logical_split = 1
.After several logical split, PageStorage V3 will throw an exception for the third time logical split and make TiFlash crash.
Here we declare the config item to be deprecated
Which TiDB version(s) do your changes apply to? (Required)
Tips for choosing the affected version(s):
By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.
For details, see tips for choosing the affected versions (in Chinese).
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?