Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
"Master/slave" terminology is offensive and not technically descriptive. Throughout the tech industry, the term "master/slave" is being replaced with contextual, more descriptive alternatives, as per the following company style guidelines:
This guide used the term "master/slave" in the context of database replication. This PR changes all uses of "master/slave" to "primary/replica". Engineers should not be using the terminology "master/slave" in interviews today, not only because it is uninclusive but also because many of the companies interviewing them are likely to disallow it.
This PR does not tackle the terms "master-master" or "multi-master", since I think there is more ambiguity around accepted alternatives for those terms. I concede it's a bit odd to have "primary/replica" terminology beside "master/master" terminology, but I felt the topic may warrant some discussion. If there is a desire to change those terms and an alignment around alternatives, I can make those changes as well.