[SERVER-26508] Mongod running as a service will not stop after migrating to a standalone wiredTiger storage engine Created: 06/Oct/16  Updated: 08/Mar/17  Resolved: 19/Nov/16

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 3.2.9, 3.2.10
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Chris Mielcarek Assignee: Kelsey Schubert
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File 2016-10-06_15-33-35.png    
Operating System: ALL
Steps To Reproduce:

Although I feel some steps may not be pertinent, they may actually contain the clue to the issue:

1. Set up mongod to run as a Windows service (using a configuration file) without authorization;
2. Run Mongo 3.0.11 with MMAPv1 as storage;
3. Upgrade Mongo to 3.2.10 as per documentation;
4. Run mongodump;
5. Edit the mongod.cfg file to contain storage.engine:wiredTiger (YAML format);
6. Stop the service;
7. Rename the \mongodb\data\db folder to db_old;
8. Create a new empty folder \mongodb\data\db;
9. Start the service;
10. Run mongorestore of the backup taken in step 4;
11. Stop the service;

      • Service fails to stop. A windows error appears. User must open task manager and kill the mongod.exe process.
Participants:

 Description   

After restoring a database the mongod service cannot stop without killing the process manually.
Windows 2012R2 using Mongo Community 3.2.10 (also 3.2.9)

Picture attached (2016-10-06_15-33-35.png) has been stuck in this state for a long time.



 Comments   
Comment by Kelsey Schubert [ 19/Nov/16 ]

Hi chrismielca,

Since some time has passed, I assume the reproduction attempt was unsuccessful. If you encounter this issue again please provide the information I requested and we will reopen the ticket to investigate.

Kind regards,
Thomas

Comment by Chris Mielcarek [ 17/Oct/16 ]

Hi Thomas,

I can't seem to reproduce, although I know this happened on my machine as well as on another colleague's machine. I will attempt again and update you.

Chris

Comment by Kelsey Schubert [ 07/Oct/16 ]

Hi chrismielca,

Thank you for reporting this issue, so we can continue to investigate would you please upload the following?

  • The complete logs of the affected mongod
  • An archive of the diagnostic.data directory

I've created a secure portal for you to use here.

Kind regards,
Thomas

Generated at Thu Feb 08 04:12:21 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.