[SERVER-19840] Replica member not "stale" but with data out of sync Created: 09/Aug/15  Updated: 10/Aug/15  Resolved: 10/Aug/15

Status: Closed
Project: Core Server
Component/s: Networking, Replication, Storage
Affects Version/s: 3.0.4
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Benjamin G Assignee: Ramon Fernandez Marina
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Steps To Reproduce:

I strictly followed this guide

http://docs.mongodb.org/manual/tutorial/deploy-replica-set/

Participants:

 Description   

Hi,

I set up a Replica set that was working properly 1 month ago. Currently, my Replica set (mongo1, mongo2, mongo3) is still up but mongo3 never gets its data updated WHEREAS commands rs.status() and rs.printSlaveReplicationInfo() show it is not "stale".

I tried to set up new Replica sets but they are all working properly like this one used to. I kept it alive in order to provide any info needed to analyse this behavior so dont hesitate to ask me anything you need to investigate.

PS: I didnt resync neither in order to keep it in its state

Thanks for your help.



 Comments   
Comment by Ramon Fernandez Marina [ 10/Aug/15 ]

No worries ibox, glad to hear you found what caused the issue.

Regards,
Ramón.

Comment by Benjamin G [ 09/Aug/15 ]

Hi, my deepest apologies, I realized someone restarted the server without the replSet option.

Sorry for the loss of time.

Thank you for the fast answer Ramon and have a good day.

Benjamin

Comment by Ramon Fernandez Marina [ 09/Aug/15 ]

ibox, have you checked the logs for the affected node? If the node is stale the logs should indicate that. Can you please post the output of rs.status() and rs.printSlaveReplicationInfo()? Having the logs for this node may come in handy as well if you can please upload them.

Thanks,
Ramón.

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