[SERVER-28135] stepdown.js should always fsyncUnlock() all secondary nodes Created: 27/Feb/17  Updated: 05/Apr/17  Resolved: 02/Mar/17

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 3.5.3
Fix Version/s: 3.2.13, 3.4.4, 3.5.4

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

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Completed:
Sprint: Repl 2017-03-06
Participants:
Linked BF Score: 0

 Description   

In stepdown.js, if there is any exception after fsync locking, the test should unlock all secondary nodes before propagating the exception.



 Comments   
Comment by Githook User [ 30/Mar/17 ]

Author:

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

Message: SERVER-28135 stepdown.js should always fsyncUnlock() all secondary nodes

(cherry picked from commit 3494a01655326a299d60f06432d7cc1bc11aecd6)
Branch: v3.2
https://github.com/mongodb/mongo/commit/e567b42ef3c015e0867eed16b02d32b98cc94e23

Comment by Githook User [ 30/Mar/17 ]

Author:

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

Message: SERVER-28135 stepdown.js should always fsyncUnlock() all secondary nodes

(cherry picked from commit 3494a01655326a299d60f06432d7cc1bc11aecd6)
Branch: v3.4
https://github.com/mongodb/mongo/commit/4901ccd9fe49bd56c1c3a257d803c73246d117f5

Comment by Githook User [ 02/Mar/17 ]

Author:

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

Message: SERVER-28135 stepdown.js should always fsyncUnlock() all secondary nodes
Branch: master
https://github.com/mongodb/mongo/commit/3494a01655326a299d60f06432d7cc1bc11aecd6

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