[SERVER-8571] no warning if restart mongod with --master instead of --replSet Created: 14/Feb/13  Updated: 06/Dec/22  Resolved: 23/Aug/18

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

Type: Improvement Priority: Minor - P4
Reporter: Dwight Merriman Assignee: Backlog - Replication Team
Resolution: Done Votes: 0
Labels: tertiary
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Replication
Participants:

 Description   

If one has been running as a replica set member, and then restarts with --master, mongod gives no warning and just goes at it, creating the non-replset local.oplog.$main collection.

If on purpose that would be semi-ok but it is likely in such as scenario to be user error so we should do something either 1) warn, 2) disallow, or something.

If disallowed we should tell people how to do this on purpose – for example, backing up and then deleting their local database before starting back up with --master would be one approach. --master is deprecated so a warning might suffice.



 Comments   
Comment by Spencer Brody (Inactive) [ 23/Aug/18 ]

master/slave has been removed

Generated at Thu Feb 08 03:17:48 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.