couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Wenk (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-2248) Replace "master" and "slave" terminology
Date Tue, 27 May 2014 07:02:02 GMT


Andy Wenk commented on COUCHDB-2248:

I have never thought in the way, that master and slave are racially charged terms in this
context. And I don't see it. These terms are very well known in the database world. I admit
that one can think, that it sounds rude, but I do not expect a technical involved person to
think like this (I just had a discussion about the well known German word "Technologische
Führerschaft" where "Führer" means leader and "Führer" was the commonly used word for Adolf
Hitler. But because the word is perfectly describing the context, we did not change it although
my brain shivers all the time I read or spell it).

For me, it would be confusing to change the wording and I think it would also confuse many
users. I like the word peer, but unfortunately it is misleading because one is reminded of
the BitTorrent protocol or the PPSPP protocol (

I do like "multi-master" replication. That would be clear and would not confuse people by
changing already well known terms.  

> Replace "master" and "slave" terminology
> ----------------------------------------
>                 Key: COUCHDB-2248
>                 URL:
>             Project: CouchDB
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Documentation
>            Reporter: Noah Slater
>            Priority: Trivial
> Inspired by the comments on this PR:
> Summary is: `master` and `slave` are racially charged terms, and it would be good to
avoid them. Django have gone for `primary` and `replica`. But we also have to deal with what
we now call multi-master setups. I propose "peer to peer" as a replacement, or just "peer"
if you're describing one node.
> As far as I can tell, the primary work here is the docs. The wiki and any supporting
material can be updated after.

This message was sent by Atlassian JIRA

View raw message