[SERVER-4373] Windows service should "do the right thing" after a crash Created: 26/Nov/11  Updated: 06/Feb/23  Resolved: 06/Feb/23

Status: Closed
Project: Core Server
Component/s: Admin
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Tad Marshall Assignee: [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive)
Resolution: Won't Do Votes: 0
Labels: Windows, community-team, platforms-re-triaged, sdp-backlog-purge
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows, mongod.exe installed as a Windows service using "mongod --install"


Issue Links:
Related
related to SERVER-3582 Mongo Windows Service locks up CPU wh... Closed
related to SERVER-3942 MongoDB service on Windows infinitely... Closed
Assigned Teams:
Server Development Platform
Operating System: Windows
Participants:

 Description   

When MongoDB is installed as a service on Windows, users will have an expectation that the database will keep itself available across system restarts. It does this fine when the system is shut down in an orderly way, but on a power failure or bluescreen or system crash, mongod.exe can't start up without some handholding because of the leftover mongod.lock file. If we just auto-restart, we fail immediately because of the leftover file. If we don't auto-restart, then users will wonder why we're not running and have to go do something to fix it.

It would be a lot better if we had a scheme for climbing out of this ditch and could make the code just recover automatically (when possible) and issue notifications to administrators to please come and intervene when that is required.



 Comments   
Comment by Iryna Zhuravlova [ 16/Nov/22 ]

After a careful backlog refinement, the team decided to close this ticket because of its low priority and limited resource capacity. If you believe that this ticket requires additional attention from the team and should be re-opened, feel free to change the status to "Needs Scheduling" and ping me or @alexander.neben

Comment by Eliot Horowitz (Inactive) [ 26/Nov/11 ]

tricky to get right

Comment by Tad Marshall [ 26/Nov/11 ]

This bug is inspired by (fallout from?) SERVER-3582 – Mongo Windows Service locks up CPU when computer reboots after a crash. In fixing that bug, I changed our behavior from "infinite failure loop" to "do nothing". It would be much better to "do the right thing", once we figure out what that is.

Generated at Thu Feb 08 03:05:48 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.