[SERVER-11826] DataFileSync thread should shutdown its Client cleanly Created: 22/Nov/13 Updated: 06/Dec/22 Resolved: 14/Sep/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | MMAPv1, Stability |
| Affects Version/s: | 2.4.8 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tom Robinson | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | mongod, shutdown, windows | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Windows Server 2012 R2 (64-bit) port=27017 |
||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Operating System: | Windows | ||||||||
| Participants: | |||||||||
| Description |
|
The MongoDB documentation suggests that the MongoDB service should just be shut down via the Windows Service Control Manager: net stop MongoDB When I did this recently, the following was logged and I ended up with a non-zero byte mongod.lock file on disk. (I used the --repair option to fix this but it turns out this probably wasn't necessary as I had journalling enabled.) Thu Nov 21 11:08:12.011 [serviceShutdown] got SERVICE_CONTROL_STOP request from Windows Service Control Manager, will terminate after current cmd ends |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 27/Nov/13 ] |
|
temporary fix for |
| Comment by Eliot Horowitz (Inactive) [ 27/Nov/13 ] |
|
At shutdown, this is a purely cosmetic issue. |
| Comment by Tom Robinson [ 22/Nov/13 ] |
|
StackOverflow posting that prompted this bug report: Possible related issue: |