Replaced "master/slave" terminology with "primary/replica"

By webchick on 14 June 2014

Change record status:

Published (View all published change records)

Project:

Drupal core

Introduced in branch:

8.x

Issue links:

https://www.drupal.org/node/2275877

Description:

Both due to negative connotations of the phrase, as well as for better accuracy, "master/slave" has been replaced in the code base to "primary/replica." This pairing is used not only in Django, but also IBM Rational ClearQuest, Microsoft System Center, Engine Yard, and AWS.

Changes for site builders

Instead of specifying $databases['default']['slave'][] = $info_array; in settings.php, now you specify $databases['default']['replica'][] = $info_array;

API changes

'target' => 'slave' in db_select()/queryRange()/etc. changed to 'target' => 'replica'
db_ignore_slave() => db_ignore_replica()
class SlaveDatabaseIgnoreSubscriber => class ReplicaDatabaseIgnoreSubscriber
"slave" key in Views options renamed to "replica"

Updates Done (doc team, etc.)

Online documentation:

Not done

Theming guide:

Not done

Module developer documentation:

Not done

Examples project:

Not done

Coder Review:

Not done

Coder Upgrade:

Not done

Other:

Other updates done

Comments

Better reasons

rachel_norfolk

English

commented 14 June 2014 at 14:52

I like the change but I'm not sure about the reasoning as such.

I would much rather see the reason for this change being as positive as the actual change. Simply the fact that primary/replica describes better what is actually going on on with replication than master/slave certInly does this.