[SERVER-9396] otherLock cache variable was not working Created: 18/Apr/13 Updated: 11/Jul/16 Resolved: 18/Apr/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Concurrency |
| Affects Version/s: | 2.2.0 |
| Fix Version/s: | 2.5.0 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Dwight Merriman | Assignee: | Dwight Merriman |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
There was a regression where this broke long ago - in 2.1.x i think. Anyway, the otherLock variable is zeroed everytime in the broken variant which makes us have to hit a mutex (in DBLocksMap which is a mapsf) to look up the right db lock as part of that process. The lookup is quick so it is a low P bug. |
| Comments |
| Comment by auto [ 18/Apr/13 ] |
|
Author: {u'date': u'2013-04-18T19:19:52Z', u'name': u'Dwight', u'email': u'dwight@10gen.com'}Message: |