[SERVER-6494] Inconsistent behavior with rs.add and rs.reconfigure Created: 17/Jul/12  Updated: 30/Jul/12  Resolved: 18/Jul/12

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

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
Operating System: ALL
Participants:

 Description   

Reported from the Google groups:

https://groups.google.com/forum/?fromgroups#!topic/mongodb-user/eXZfE8EprBI

Description from user:

1) restore host.com with latest backup (including oplog) and execute
rs.add("host.com") - and you'll that data will be deleted and resynced
from scratch
2) restore host.com with latest backup (including oplog) and add it
into the replica set with rs.reconfig - it will be catched up as slave
almost immediately
3) try to reconfigure one of shards with rs.add and rs.reconfig - and
check the mongoses logs - you'll see the difference


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