[SERVER-4619] Relinquishing primary should be done in write lock Created: 04/Jan/12  Updated: 11/Jul/16  Resolved: 07/Mar/12

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 2.0.5, 2.1.1

Type: Bug Priority: Major - P3
Reporter: Kristina Chodorow (Inactive) Assignee: Kristina Chodorow (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Operating System: ALL
Participants:

 Description   

Becoming primary is syncronized with a write lock, but there's a race condition in relinquish where you could change state to secondary, write ops could happen, then sockets were closed.



 Comments   
Comment by auto [ 17/Apr/12 ]

Author:

{u'login': u'kchodorow', u'name': u'Kristina', u'email': u'kristina@10gen.com'}

Message: Extend writelock during stepdown to include socket close SERVER-4619
Branch: v2.0
https://github.com/mongodb/mongo/commit/b32511d875786fe2428e275e198cdbeccfeb4c1e

Comment by Richard Kreuter (Inactive) [ 07/Mar/12 ]

Reopening because I'd like to ask for a backport to 2.0.

Comment by auto [ 13/Feb/12 ]

Author:

{u'login': u'kchodorow', u'name': u'Kristina', u'email': u'kristina@10gen.com'}

Message: Extend writelock during stepdown to include socket close SERVER-4619
Branch: master
https://github.com/mongodb/mongo/commit/715ba7106637aa04091d54e6edb2655b1bbdf991

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