[SERVER-4281] isMaster command hangs if db is fsyncLocked and authentication is enabled Created: 14/Nov/11 Updated: 29/Jun/12 Resolved: 16/Nov/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Security |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
Steps to reproduce: Doing the same thing without authentication does not cause it to hang. |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 16/Nov/11 ] |
|
correct fix is |
| Comment by Spencer Brody (Inactive) [ 15/Nov/11 ] |
|
I'm not sure what the best way to address this is. When using authentication, the isMaster command needs to check if it has permissions to run, and to do that it gets a read lock. When fsync locked with a write pending, the read lock can't be taken, which causes this command to hang. Short of fixing |