[SERVER-6364] Remove/replace write lock in replAuthenticate() Created: 09/Jul/12  Updated: 19/Mar/13  Resolved: 11/Mar/13

Status: Closed
Project: Core Server
Component/s: Security
Affects Version/s: 2.0.6, 2.1.2
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: Ben Becker Assignee: Unassigned
Resolution: Done Votes: 0
Labels: Authentication., ReplSet
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

All


Issue Links:
Related
is related to SERVER-7428 can't lock_W, threadState=119; cero_p... Closed
Participants:

 Description   

In repl.cpp (L1056 in r2.0.2; L1069 in master), we take a write lock before calling findOne() or getSingleton(). There doesn't seem to be a reason for taking a write lock here; replacing with a read lock seems to make sense.



 Comments   
Comment by Ben Becker [ 11/Mar/13 ]

Issue was resolved by SERVER-7428.

Comment by Eric Milkie [ 11/Mar/13 ]

The line in question seems to have already been switched to a ReadContext sometime prior to version 2.2.

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