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

[#7846, #11532] Update xcluster docs #11534

Merged
merged 4 commits into from
Feb 19, 2022
Merged

Conversation

bmatican
Copy link
Contributor

Updating the feature and limitations section of the xcluster docs:

  • Remove references to master / slave
  • Beef up topology section
  • Changed main Features section to talk about the architectural pieces (eg: at-least-once semantics, multi-shard txns, conflict resolution)
  • Polished Limitations section
    • Added GH issues to some known items
    • Beef up DDL section with mentions to DROP & TRUNCATE
    • Added Scalability section
    • Added Kubernetes section
    • Added cross-feature integration section with Supported and Not yet supported sub-sections

Still has a couple of TBD items, mostly for GH issues, pending eng and product review.

@netlify
Copy link

netlify bot commented Feb 18, 2022

✔️ Deploy Preview for infallible-bardeen-164bc9 ready!

🔨 Explore the source changes: 1fbc961

🔍 Inspect the deploy log: https://app.netlify.com/sites/infallible-bardeen-164bc9/deploys/621053cf636e2d0008233054

😎 Browse the preview: https://deploy-preview-11534--infallible-bardeen-164bc9.netlify.app

Copy link
Contributor

@hulien22 hulien22 left a comment

Choose a reason for hiding this comment

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

Believe the rest of the TBD GH issues don't have issues atm

Copy link
Contributor

@ymahajan ymahajan left a comment

Choose a reason for hiding this comment

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

@bmatican Thanks for doing this, changes look good to me for the first pass. We need to use 'Source' and 'Target' terms everywhere (rather than producer, consumer, sink and so on). It's okay to create a follow-up PR to rename these terms.

@bmatican
Copy link
Contributor Author

@ymahajan Agreed on changing to one single terminology, but we also have diagrams which would have to change and I didn't want to touch those..

@bmatican bmatican merged commit c64c051 into yugabyte:master Feb 19, 2022
jayant07-yb pushed a commit to jayant07-yb/yugabyte-db that referenced this pull request Mar 8, 2022
Remove references to master / slave
Beef up topology section
Changed main Features section to talk about the architectural pieces (eg: at-least-once semantics, multi-shard txns, conflict resolution)
Polished Limitations section
Added GH issues to some known items
Beef up DDL section with mentions to DROP & TRUNCATE
Added Scalability section
Added Kubernetes section
Added cross-feature integration section with Supported and Not yet supported sub-sections
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