[MDEV-18264] Rename Master/Slave Created: 2019-01-16 Updated: 2019-09-14 Resolved: 2019-09-14 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Documentation, Replication |
| Fix Version/s: | N/A |
| Type: | Task | Priority: | Major |
| Reporter: | Manjot Singh (Inactive) | Assignee: | Jacob Moorman (Inactive) |
| Resolution: | Duplicate | Votes: | 1 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Description |
|
Consider renaming Master/Slave to: https://en.wikipedia.org/wiki/Master/slave_(technology)#Terminology_concerns The first iteration could be aliases for: |
| Comments |
| Comment by John Sheaffer (Inactive) [ 2019-01-16 ] |
|
When talking to customers who prefer to avoid using the master/slave nomenclature, I most commonly hear "Primary/Replica" used as the alternate. |
| Comment by Daniel Black [ 2019-01-16 ] |
|
Master/Replica might be a good first term as at least existing master/slave documentation will be readable and that Slave->Replica is the only substitution. It also 1/2s the number of terms changed in the code. For comparison, I looked at Postgres which seems to user Primary/Standby (and I don't think standby is a good fix here because it can be a fully active in MySQL). Reinforces "primary" as a good master replacement however. |
| Comment by Jacob Moorman (Inactive) [ 2019-05-13 ] |
|
Analysis is occurring via DOCS-308. |