-
Notifications
You must be signed in to change notification settings - Fork 205
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
Document reference tables #1849
Conversation
Signed-off-by: Rohit Nayak <[email protected]>
✅ Deploy Preview for vitess ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
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.
Love it! Thank you for this.
content/en/docs/21.0/reference/vreplication/reference_tables.md
Outdated
Show resolved
Hide resolved
content/en/docs/21.0/reference/vreplication/reference_tables.md
Outdated
Show resolved
Hide resolved
content/en/docs/21.0/reference/vreplication/reference_tables.md
Outdated
Show resolved
Hide resolved
content/en/docs/21.0/reference/vreplication/reference_tables.md
Outdated
Show resolved
Hide resolved
content/en/docs/21.0/reference/vreplication/reference_tables.md
Outdated
Show resolved
Hide resolved
The VReplication Materialize workflow is the mechanism that you can use to keep reference tables in sync | ||
with the source across all shards. An example of how to create such a workflow is: | ||
|
||
`Materialize --target-keyspace target --workflow ref1 create --source-keyspace source --reference --tables |
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.
Better to show the full vtctldclient command IMO.
content/en/docs/21.0/reference/vreplication/reference_tables.md
Outdated
Show resolved
Hide resolved
Signed-off-by: Rohit Nayak <[email protected]>
Signed-off-by: Rohit Nayak <[email protected]>
content/en/docs/21.0/reference/vreplication/reference_tables.md
Outdated
Show resolved
Hide resolved
content/en/docs/21.0/reference/vreplication/reference_tables.md
Outdated
Show resolved
Hide resolved
content/en/docs/21.0/reference/vreplication/reference_tables.md
Outdated
Show resolved
Hide resolved
content/en/docs/21.0/reference/vreplication/reference_tables.md
Outdated
Show resolved
Hide resolved
content/en/docs/21.0/reference/vreplication/reference_tables.md
Outdated
Show resolved
Hide resolved
content/en/docs/21.0/reference/vreplication/reference_tables.md
Outdated
Show resolved
Hide resolved
content/en/docs/21.0/reference/vreplication/reference_tables.md
Outdated
Show resolved
Hide resolved
content/en/docs/21.0/reference/vreplication/reference_tables.md
Outdated
Show resolved
Hide resolved
content/en/docs/21.0/reference/vreplication/reference_tables.md
Outdated
Show resolved
Hide resolved
replication. If the load on the source and/or target is high, it is possible that there is a lag between the source | ||
getting updated and those updates being propagated to the target. | ||
|
||
You can monitor the lag by using `Workflow Show` on the workflows and looking at the value for the |
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.
We should also say that you can monitor this from VTAdmin UI. Extra credit: screenshot showing a workflow in VTAdmin.
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.
Once Noble has the details page completed we will add a common page for VTAdmin monitoring with screenshots and we can link to it.
Signed-off-by: Rohit Nayak <[email protected]>
Generic reference tables page as a complement to vitessio/vitess#16787.
Related page: https://deploy-preview-1849--vitess.netlify.app/docs/21.0/reference/vreplication/reference_tables/