[SERVER-24725] Hidden Member switched sync source multiple times and then crashes during rollback Created: 22/Jun/16  Updated: 14/Jul/16  Resolved: 08/Jul/16

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

Type: Bug Priority: Minor - P4
Reporter: Darshan Shah Assignee: Kelsey Schubert
Resolution: Duplicate Votes: 0
Labels: RF
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File mongod.log.txt     Zip Archive primary_mongod.zip     Zip Archive secondary_mongod.zip    
Issue Links:
Duplicate
duplicates SERVER-7200 use oplog as op buffer on secondaries Closed
Operating System: ALL
Participants:

 Description   

We have a tag-aware sharded cluster with each node being a 3 member replicaset of which 1 member is hidden.

In this particular instance, the hidden member keeps switching the sync source between Primary & the other Secondary and rolls back updates after every switch.

After a couple of such switches and rollbacks, it enters into an invalid/inconsistent state and crashes.

Attached is the log file for the mongod instance showing this.



 Comments   
Comment by Kelsey Schubert [ 08/Jul/16 ]

Hi darshan.shah@interactivedata.com,

Thank you for providing the complete logs; they align with my previous hypothesis so I will be closing this ticket as a duplicate. Please watch SERVER-7200 for updates.

Kind regards,
Thomas

Comment by Darshan Shah [ 24/Jun/16 ]

Log files from primary & secondary mongod from the same time we see the issue in the hidden secondary.

Comment by Darshan Shah [ 24/Jun/16 ]

Hi Thomas,

Thanks for checking and providing details.

Attaching the logs from the primary and secondary mongod logs from that time for your reference.
Please review and let me know if these logs confirm your suspicion.

Thanks.

Comment by Kelsey Schubert [ 23/Jun/16 ]

Hi darshan.shah@interactivedata.com,

Thanks for reporting this behavior. I believe the issue you describe will be corrected by SERVER-7200. For additional discussion relating to the error you observed, please see its linked ticket, SERVER-23841. To confirm this diagnosis, would you please upload the logs from the other members of the replica set?

Kind regards,
Thomas

Generated at Thu Feb 08 04:07:14 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.