[SERVER-40368] Clustered Host Fails to Start - After Disabling Replication Created: 28/Mar/19 Updated: 25/Apr/19 Resolved: 25/Apr/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Steven B. | Assignee: | Danny Hatcher (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Steps To Reproduce: | Shutting down host via "service mongodb stop" systemctl --no-block start mongod |
| Participants: |
| Description |
|
MongoDB exits each time the application is started.
|
| Comments |
| Comment by Danny Hatcher (Inactive) [ 03/Apr/19 ] | |
|
Hello Steven, I'm glad to hear that you were able to resolve your startup issue. The database shouldn't take that long to startup with 200GB of data. Could you provide mongod logs showing that long startup time? Thanks, Danny | |
| Comment by Steven B. [ 01/Apr/19 ] | |
|
Thank you for replying. I was able to resolve the issue by making the following change. /lib/systemd/system/mongod.service However startup times are extremely slow. The database is ~200GB in size and I'm questioning if WiredTiger is the most appropriate storage engine. Could you point me towards some resources which will help end my dilemma? | |
| Comment by Danny Hatcher (Inactive) [ 28/Mar/19 ] | |
|
Hello Steven, Something outside the mongod process itself is calling for the process to shutdown:
Could you please clarify the steps that you are performing to get to this state and where you think the problem is? Thank you, Danny |