[SERVER-4360] replica sets Created: 23/Nov/11  Updated: 29/Feb/12  Resolved: 23/Nov/11

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

Type: Bug Priority: Major - P3
Reporter: Balamurugan Assignee: Unassigned
Resolution: Done Votes: 0
Labels: replication
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Live


Operating System: Linux
Participants:

 Description   

We have 3 server replica setup - 2 data servers + 1 arbiter (Primary and Secondary).
1. Mongo is going down on a primary - server1.
2. Now, the secondary is a primary - server2.
3. Insert some value (Data available in the primary server - server2).
4. Now, the primary is down - server2.
5. First, we up the server1. (Now Server1 is primary)
6. Second , we up the server2. (Server2 is secondary)
The insert data not available in servers, because replication done in primary to secondary. suppose we up the server2 first (primary) the data available.

How to fix this issue.



 Comments   
Comment by Scott Hernandez (Inactive) [ 23/Nov/11 ]

It sounds like you had a rollback: http://www.mongodb.org/display/DOCS/Replica+Sets+-+Rollbacks

If you need data on more than one replica after each write you must use a WriteConcern.REPLICA_SAFE (getLastError w>1): http://www.mongodb.org/display/DOCS/Verifying+Propagation+of+Writes+with+getLastError

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