[SERVER-48917] Stop using master/slave terms Created: 17/Jun/20  Updated: 06/Dec/22

Status: Open
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Noel MacLoughlin Assignee: Backlog - Service Architecture
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
Assigned Teams:
Service Arch
Participants:

 Description   

MongoDB must adopt the terms primary/secondary to replacement for unacceptable master/slave colonial terminology.  The scope of this epic should address the present future time (let's turn the page on history).



 Comments   
Comment by Lauren Lewis (Inactive) [ 05/Apr/22 ]

This issue was in the 'Investigating' status but assigned to the backlog user, so I'm moving to Needs Scheduling blake.oler

Comment by Steven Vannelli [ 22/Feb/21 ]

Hi all, please see the comment on SERVER-20608 for an update on what has been done thus far with regards to this work.

There are a few remaining references that will be addressed in the subsequent projects linked to this ticket. We will provide an update once those projects have been completed.

Comment by Evin Roesle [ 24/Jun/20 ]

Work has begun on a project to begin auditing our repository, removing the master/slave terminology and backporting those changes. MongoDB is also creating additional projects to address other terminologies that should be removed.

Comment by Noel MacLoughlin [ 17/Jun/20 ]

Please rename to "Adopt primary/secondary terms across all products".

Generated at Thu Feb 08 05:18:25 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.