-
Notifications
You must be signed in to change notification settings - Fork 82
Rewrite the introduction to the Clustering section #2749
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
base: dev
Are you sure you want to change the base?
Rewrite the introduction to the Clustering section #2749
Conversation
modules/ROOT/pages/clustering/multi-region-deployment/geo-redundant-deployment.adoc
Show resolved
Hide resolved
6b095c3 to
87a6450
Compare
modules/ROOT/pages/clustering/multi-region-deployment/geo-redundant-deployment.adoc
Outdated
Show resolved
Hide resolved
| Servers and databases are decoupled: servers provide computation and storage power for databases to use. | ||
| Each database relies on its own cluster architecture, organized into primaries (with a minimum of three for high availability) and secondaries (for read scaling). | ||
| . *Fault tolerance:* Primary database allocations provide a fault tolerant platform for transaction processing. | ||
| A database remains available for reads and writes as long as a simple majority of its primary copies are functioning. |
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.
copies -> allocations
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.
Hmm depends actually, are we using copy/allocation interchangeably elsewhere? In which ignore this suggestion.
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.
It might be good to use database allocation everywhere though.
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.
In fact, we're using copies/allocations interchangeably. In the Disaster recovery, however, we decided to use allocations only.
| That means they can host standard databases only in primary mode or only in secondary mode. | ||
| If the `modeConstraint` is set to `NONE`, a server can host databases in either mode. | ||
| In other words, a server can host primaries for some databases and secondaries for other databases. |
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 use both role and mode here to refer to the same concept, maybe this is ok but might be better for readers to be consistent
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.
I agree, but at the same time we use 'modeConstraint', 'server.cluster.system_database_mode' and the 'roles' column in the SHOW DATABASES output. So, there is some inconsistency in the code.
Which term is preferable in your opinion?
87a6450 to
af0d43a
Compare
|
This PR includes documentation updates Updated pages: |
Rewrite the Clustering introductory page to include examples of database topologies.
Remove terminology inconsistencies across a few pages.