Skip to content

removed explanations of RBR vs SBR, we now support RBR#3876

Merged
sougou merged 3 commits intovitessio:masterfrom
jvaidya:fix_rbr
May 1, 2018
Merged

removed explanations of RBR vs SBR, we now support RBR#3876
sougou merged 3 commits intovitessio:masterfrom
jvaidya:fix_rbr

Conversation

@jvaidya
Copy link
Copy Markdown
Contributor

@jvaidya jvaidya commented Apr 30, 2018

Signed-off-by: jvaidya jitendra.vaidya@gmail.com

Signed-off-by: jvaidya <jitendra.vaidya@gmail.com>
Copy link
Copy Markdown
Contributor

@alainjobart alainjobart left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Feel free to merge after change is made.

row based. Vitess supports both these modes.

For schema changes, if the number of affected rows is greater > 100k (configurable), we don't allow direct application
of DDLs the recommended tool in such cases is gh-ost
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

of DDLs the recommended tool in such cases is gh-ost
Should probably be:
of DDLs. The recommended tool in such cases is gh-ost.
And link to the gh-ost project.

row based. Vitess supports both these modes.

For schema changes, if the number of affected rows is greater > 100k (configurable), we don't allow direct application
of DDLs the recommended tool in such cases is gh-ost
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

DDLs. The recommend...

to provide the same features when possible. See Appendix for our plan.
When using statement based replication, Vitess helps by rewriting Update statements,
therefore allowing complex schema changes, while at the same time simplifying the replication stream (so
slaves can be fast). This is described in detail below.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Replace with:
Not all statements are safe for SBR: https://dev.mysql.com/doc/refman/8.0/en/replication-rbr-safe-unsafe.html. Vitess rewrites some of these statements to be safe for SBR, and others are explicitly failed.


Thus, with statement based replication, it becomes easier to perform offline
advanced schema changes, or large data updates. Vitess’s solution is called
schema swap (described below).
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The schema swap is independent of vitess's statement rewrites.

Signed-off-by: jvaidya <jitendra.vaidya@gmail.com>
Copy link
Copy Markdown
Contributor

@sougou sougou left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@derekperkins
Copy link
Copy Markdown
Member

Are we recommending gh-ost over pt-osc?

@sougou
Copy link
Copy Markdown
Contributor

sougou commented Apr 30, 2018

Maybe recommend both?

Signed-off-by: jvaidya <jitendra.vaidya@gmail.com>
@sougou sougou merged commit eb92663 into vitessio:master May 1, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants