[SERVER-2708] [Replica set slave delay] Stale delayed slave reports status as "recovering" Created: 08/Mar/11  Updated: 29/Aug/11  Resolved: 17/Mar/11

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

Type: Bug Priority: Major - P3
Reporter: Kyle Banker Assignee: Kristina Chodorow (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   
  • Create a slavedelayed node in a replica set.
  • Get it to age out its oplog.
  • Notice that the staleness is reported in the logs while rs.status() reports that it's still in state 3 ("RECOVERING")
  • Shoud be "FATAL"


 Comments   
Comment by Kristina Chodorow (Inactive) [ 17/Mar/11 ]

I think this is the correct behavior. For example, suppose it's now 10pm and the master oplog's earliest time is 8pm, and the secondary has only synced to 6pm. However, another secondary might come online that has an oplog spanning from 5pm->10pm (now). Then the stale slave can suddenly jump back in and sync up from that secondary.

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