[SERVER-5100] writelocktry in replMasterThread may make reads hang Created: 26/Feb/12 Updated: 11/Jul/16 Resolved: 05/Jun/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Concurrency, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 2.1.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Ian Whalen (Inactive) | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | buildbot | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
OS X 10.5 64-bit DEBUG |
||
| Issue Links: |
|
||||||||||||||||
| Operating System: | OS X | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
|
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 02/Mar/12 ] |
|
This is fixed by |
| Comment by Eric Milkie [ 02/Mar/12 ] |
|
filed |
| Comment by Eric Milkie [ 27/Feb/12 ] |
|
I am looking at the hung test on the Linux 32bit builder. When I debugged the mongo process, all the threads were blocked waiting for output from the mongod's it had spawned, except for thread 1. Thread 1 was blocked in the js interpreter, on a JSSleep call. So presumably it's in a sleep loop in the test code. It seems that the scenario proposed in |