Skip to content
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

Merged
merged 4 commits into from
Oct 3, 2024
Merged

Document reference tables #1849

merged 4 commits into from
Oct 3, 2024

Conversation

rohit-nayak-ps
Copy link
Contributor

@rohit-nayak-ps rohit-nayak-ps commented Sep 16, 2024

Signed-off-by: Rohit Nayak <[email protected]>
Copy link

netlify bot commented Sep 16, 2024

Deploy Preview for vitess ready!

Name Link
🔨 Latest commit 6d1806b
🔍 Latest deploy log https://app.netlify.com/sites/vitess/deploys/66fe6e26994f6a0009019cb2
😎 Deploy Preview https://deploy-preview-1849--vitess.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link
Collaborator

@mattlord mattlord left a 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.

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
Copy link
Collaborator

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.

@rohit-nayak-ps rohit-nayak-ps marked this pull request as ready for review September 29, 2024 14:43
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
Copy link
Member

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.

Copy link
Contributor Author

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]>
@rohit-nayak-ps rohit-nayak-ps merged commit 8eb5625 into prod Oct 3, 2024
5 checks passed
@rohit-nayak-ps rohit-nayak-ps deleted the rohit/reference branch October 3, 2024 10:15
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.

3 participants