[SERVER-16147] Fail initial sync if cloner has index/data errors Created: 14/Nov/14  Updated: 24/Nov/14  Resolved: 14/Nov/14

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

Type: Bug Priority: Critical - P2
Reporter: Scott Hernandez (Inactive) Assignee: Scott Hernandez (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:
Linked BF Score: 0

 Description   

There were code paths which didn't increment the failed count to trigger the fassert. This led to initial sync retrying forever.



 Comments   
Comment by Githook User [ 14/Nov/14 ]

Author:

{u'username': u'scotthernandez', u'name': u'Scott Hernandez', u'email': u'scotthernandez@gmail.com'}

Message: SERVER-16147: get oplog source in loop
Branch: master
https://github.com/mongodb/mongo/commit/3660339e223ce36e864e983ef3e4b419738e54c4

Comment by Githook User [ 14/Nov/14 ]

Author:

{u'username': u'scotthernandez', u'name': u'Scott Hernandez', u'email': u'scotthernandez@gmail.com'}

Message: SERVER-16147: do not retry initial sync forever
Branch: master
https://github.com/mongodb/mongo/commit/47d13ec4b8f19973cd7242ea2cba2ec882073a5e

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