[SERVER-17179] check for replicaset stepdown in cloner Created: 04/Feb/15  Updated: 18/Sep/15  Resolved: 05/Feb/15

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.0.0-rc8

Type: Bug Priority: Major - P3
Reporter: Eric Milkie Assignee: Benety Goh
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-17150 logOp fassert when dropping collectio... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: RPL 0 3/13/15
Participants:

 Description   

A few places where we lock or relock a DBLock, we are failing to check canAcceptWritesFor().



 Comments   
Comment by Githook User [ 05/Feb/15 ]

Author:

{u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}

Message: SERVER-17179 check for primary step down in cloner

(cherry picked from commit d4ab26fcfb6d4dc64d7067fd0b5ba08090cf5c59)
Branch: v3.0
https://github.com/mongodb/mongo/commit/0c06c7307aae2509e5d22835261b124427a8754b

Comment by Githook User [ 05/Feb/15 ]

Author:

{u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}

Message: SERVER-17179 check for primary step down in cloner
Branch: master
https://github.com/mongodb/mongo/commit/d4ab26fcfb6d4dc64d7067fd0b5ba08090cf5c59

Comment by Eric Milkie [ 04/Feb/15 ]

Places to add a check in cloner.cpp:
Lines
126
178 (already present)
307 (after TempRelease unreleases)
370
538 (after TempRelease unreleases)

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