[SERVER-8498] Ambiguous behavior after replica set member recovering. Created: 11/Feb/13  Updated: 08/Mar/13  Resolved: 11/Feb/13

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

Type: Bug Priority: Trivial - P5
Reporter: Yan Tanygin Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows 7 x64


Operating System: Windows
Steps To Reproduce:

1. Create repica set (Primary, Secondary, Arbiter)
2. Insert several documents to (e.g.) test collection.
3. Stop Secondary server, run it offline and remove all documents from test collection.
4. Run Secondary and wait replica set sync is completed.
5. Stop Primary and remove all it's data.
6. Run Primary and wait replica set sync is completed.

Result: there is one document (the one that was added last) in test collection on Primary server.
Expected: test collection is empty.

Participants:

 Description   

Excess data appears after replica set member recovering.



 Comments   
Comment by Scott Hernandez (Inactive) [ 11/Feb/13 ]

The behavior of manually removing some data from different members requires internal knowledge of how replication works to predict results. Since these type of operations are not supported (removing data from members outside of normal replica set mode) this cannot be considered a bug, nor an unexpected outcome.

If you have a reasonable scenario given normal operations of a replica set please create a new issue with that information.

BTW. I think what you want to do is make sure you wipe all the files, not just your database files or collections since replication data is kept in the local database.

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