Vreplication docs: MoveTables and Resharding #415
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
morgo
force-pushed
the
morgo-vreplication-local-examples
branch
from
0428486
to
d7fe3a1
Compare
Signed-off-by: Morgan Tocker <tocker@gmail.com>
morgo
force-pushed
the
morgo-vreplication-local-examples
branch
from
d7fe3a1
to
22fddab
Compare
Signed-off-by: Morgan Tocker <tocker@gmail.com>
Signed-off-by: Morgan Tocker <tocker@gmail.com>
Signed-off-by: Morgan Tocker <tocker@gmail.com>
sougou
reviewed
Mar 27, 2020
morgo
force-pushed
the
morgo-vreplication-local-examples
branch
from
a10ce5c
to
0bde4e4
Compare
…local-examples Signed-off-by: Morgan Tocker <tocker@gmail.com>
…scale/vitess-website into morgo-vreplication-local-examples Signed-off-by: Morgan Tocker <tocker@gmail.com>
Signed-off-by: Morgan Tocker <tocker@gmail.com>
morgo
changed the title
Signed-off-by: Morgan Tocker <tocker@gmail.com>
morgo
force-pushed
the
morgo-vreplication-local-examples
branch
from
1064089
to
d5c7eda
Compare
bnlandry
reviewed
Apr 6, 2020
bnlandry
reviewed
Apr 6, 2020
bnlandry
reviewed
Apr 6, 2020
bnlandry
reviewed
Apr 6, 2020
|
|
||
| As a stepping stone towards horizontally sharding (splitting a single table across multiple servers), it usually makes sense to split from having a single monolithic keyspace (`commerce`) to having multiple keyspaces (`commerce` and `customer`) that match your access pattern. For example, in our ecommerce system we know that `customer` and `corder` tables are closely related and growing at a high rate just by themselves. | ||
|
|
||
| Lets start by simulating this situation by loading sample data: |
There was a problem hiding this comment.
Overall style note: it's often more clear to avoid the first person plural, since it creates ambiguity about who is who. Also, it can be helpful to avoid using the past and present tense, since it causes the user to mentally jump around in the sequence, which can be disorienting in a how-to guide.
bnlandry
reviewed
Apr 6, 2020
bnlandry
reviewed
Apr 6, 2020
bnlandry
reviewed
Apr 6, 2020
bnlandry
reviewed
Apr 6, 2020
bnlandry
reviewed
Apr 6, 2020
bnlandry
reviewed
Apr 6, 2020
bnlandry
reviewed
Apr 6, 2020
bnlandry
reviewed
Apr 6, 2020
bnlandry
reviewed
Apr 6, 2020
bnlandry
reviewed
Apr 6, 2020
bnlandry
reviewed
Apr 6, 2020
bnlandry
reviewed
Apr 6, 2020
|
|
||
| The next decision is about the sharding keys, aka Primary Vindexes. This is a complex decision that involves the following considerations: | ||
|
|
||
| * What are the highest QPS queries, and what are the where clauses for them? |
There was a problem hiding this comment.
Maybe: ...and what are the WHERE clauses for them?
bnlandry
reviewed
Apr 6, 2020
bnlandry
reviewed
Apr 6, 2020
bnlandry
reviewed
Apr 6, 2020
bnlandry
reviewed
Apr 6, 2020
bnlandry
reviewed
Apr 6, 2020
Signed-off-by: Morgan Tocker <tocker@gmail.com>
Signed-off-by: Morgan Tocker <tocker@gmail.com>
Signed-off-by: Morgan Tocker <tocker@gmail.com>
Change it again after Vitess 6 release. Signed-off-by: Morgan Tocker <tocker@gmail.com>
sougou
approved these changes
Apr 13, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #334
I incorporated the actual workflow steps here instead of the shell scripts. I like it more because it is more descriptive of the usage and easier to customize. The shell scripts add a level of indirection which makes it harder.
Signed-off-by: Morgan Tocker tocker@gmail.com