[SERVER-3384] When a server is "RECOVERING" and has not finished, under what conditions can it become "PRIMARY" Created: 07/Jul/11  Updated: 29/Feb/12  Resolved: 02/Sep/11

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

Type: Question Priority: Major - P3
Reporter: Edward M. Goldberg Assignee: Kristina Chodorow (Inactive)
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

AWS


Issue Links:
Duplicate
duplicates SERVER-2969 stale server should not be able to el... Closed
Participants:

 Description   

I had a server in RECOVERING status ( not finished, OpLog was too short ) and the PRIMARY Failed.

The Server Recovering became the PRIMARY server.

Under what conditions is this possible?

Side Effects:

The Collections lost data back to the age of the RECOVERING server.
The Restored server started to "ROLLBACK".

Please call any time:
Cell:     916-202-1600
Skype:  EdwardMGoldberg

Edward M. Goldberg
http://myCloudWatcher.com/
e.m.g.



 Comments   
Comment by Kristina Chodorow (Inactive) [ 07/Jul/11 ]

This was a bug in 1.8 (and earlier) that has been fixed (SERVER-2969). If the primary goes down the stale server didn't keep track of what a "non-stale" state would be, so it would elect itself.

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