[SERVER-16507] initial sync needs to lock properly before truncating oplog Created: 11/Dec/14  Updated: 18/Dec/14  Resolved: 12/Dec/14

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

Type: Bug Priority: Major - P3
Reporter: Eric Milkie 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
is depended on by SERVER-16429 Concurrent mapReduces with same repla... Closed
Related
is related to SERVER-16503 replication should obtain DB X lock w... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

seen in patch build: https://mci.10gen.com/build/mongodb_mongo_master_linux_64_ae6df7a0b10cb40c2730b10f4057454ca6733b13_14_12_11_14_34_35



 Comments   
Comment by Githook User [ 12/Dec/14 ]

Author:

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

Message: SERVER-16507: fix duplicate assert number
Branch: master
https://github.com/mongodb/mongo/commit/5950976bb7c42acec51850614edcebe6ad8bb233

Comment by Githook User [ 12/Dec/14 ]

Author:

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

Message: SERVER-16507: lock X before truncating oplog
Branch: master
https://github.com/mongodb/mongo/commit/ac80855c712ec88c207821bbc3262c575580d779

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