Rename or alias slave-related statements, options, status variables

A US-based user has asked me whether we can rename or alias slave-related statements, options, status variables. I believe that discussions involving slaves can be uncomfortable for some people due to the history of slavery in the U.S.

Aliasing can be implemented, as well as new optional command/option names. For example SHOW REPLICA STATUS as alternative to SHOW MASTER STATUS.

Existing names and output must be preserved if they can be in use by existing user application and scripts, to preserve backwards compatibility.

Newly added options and commands still need to have a variant following the main traditional terminology for consistency (eg. Master_* options for CHANGE MASTER). New optional commands could change the output naming (eg. output of SHOW REPLICA STATUS) as this does not break backwards compatibility.

Internal (non-user-facing naming) must not be changed to avoid unnecessary source code changes that complicate merges and reading commit history).

I have no idea how prevalent this feeling is, but I do know that several other software teams have done similar changes recently. For example:

https://www.theregister.co.uk/2018/09/11/python_purges_master_and_slave_in_political_pogrom/

https://www.theregister.co.uk/2018/09/13/redis_master_slave/

https://github.com/antirez/redis/issues/5335

https://github.com/kubernetes/website/issues/6525

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

If we did want to do this, then some potential replacements are:

• replica
• clone
• replicator
• standby
• secondary
• follower