[SERVER-4277] Creating new shell while fsync locked with authentication hangs. Created: 14/Nov/11 Updated: 04/Apr/14 Resolved: 16/Nov/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Security, Shell |
| 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: This can leave you unable to fsyncUnlock if you accidentally try to write data while fsyncLocked. |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 16/Nov/11 ] |
|
correct fix is |
| Comment by Spencer Brody (Inactive) [ 14/Nov/11 ] |
|
The problem is that for some reason the isMaster command hangs when the db is fsync locked and authentication is enabled. If the db is fsync locked without authentication (or authentication is on without fsync locking), the isMaster command works fine. |
| Comment by Spencer Brody (Inactive) [ 14/Nov/11 ] |
|
There is actually an issue specific to using authentication which is that the shell hangs on startup rather than after issuing the first read query, which can leave you unable to fsync unlock. |