-
-
Notifications
You must be signed in to change notification settings - Fork 141
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(tianmu): fix problems related to master slave synchronization (#819) #877
Conversation
Thanks for the contribution! Please review the labels and make any necessary changes. |
5445dd0
to
4eb5bf5
Compare
CR, PTAL, @RingsC @hustjieke @isredstar @duanfuxiang0 |
4eb5bf5
to
e77fea1
Compare
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
@konghaiya pls fix the review comment. |
25cf2b1
to
d00a3fb
Compare
2c8d24a
to
04da0c4
Compare
…oneatom#819) fix 1:stoneatom#818 Master slave synchronization - There will be too many tuples problem Cause: Tianmu::dbhandler::TianmuHandler::current_position This variable is not initialized. In some cases, a large value may cause too many tuples problem. Solution: Initialize the variable fix 2:stoneatom#819 Master slave synchronization - Primary key conflict problem Solution: Modify the modification logic of master slave synchronization, so that the delete and update operations do not follow the primary key logic Supplement sql/sql_insert.cc Fix the problem that the insert statement will not generate binlog in the delayed insert mode storage/tianmu/handler/tianmu_handler.cpp Fix the binlog error of the line format generated by the tianmu engine
04da0c4
to
bacd9a7
Compare
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
fix 1:#818 Master slave synchronization - There will be too many tuples problem
Cause:
Tianmu::dbhandler::TianmuHandler::current_position This variable is not initialized. In some cases, a large value may cause too many tuples problem.
Solution: Initialize the variable
fix 2:#819 Master slave synchronization - Primary key conflict problem
Solution: Modify the modification logic of master slave synchronization, so that the delete and update operations do not follow the primary key logic
Supplement
sql/sql_insert.cc
Fix the problem that the insert statement will not generate binlog in the delayed insert mode storage/tianmu/handler/tianmu_handler.cpp
Fix the binlog error of the line format generated by the tianmu engine
Summary about this PR
Issue Number: close #issue_number_you_created
Tests Check List
Changelog
Documentation