[SERVER-779] make a couple commands not use write locks Created: 18/Mar/10 Updated: 12/Jul/16 Resolved: 08/Sep/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.7.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Aaron Staple | Assignee: | Aaron Staple |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
I think we can probably do isinitialsynccomplete without any lock. Just glancing at authenticate it seems like we can make it use a read lock if we just get rid of an OCCASIONALLY ensureIndex(), which presumably we could just put somewhere else. |
| Comments |
| Comment by Aaron Staple [ 08/Sep/10 ] |
|
The weird auth/lock code has been changed, so I don't think this is strictly necessary anymore. It was easier to leave authenticate as a write command, so I did so. |
| Comment by auto [ 08/Sep/10 ] |
|
Author: {'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}Message: |