Скачать или смотреть Understanding Why MongoDB Automatically Restarts After Shutdown

Discover the reasons behind unexpected auto-restarts of `MongoDB` after a shutdown and learn how to manage MongoDB services effectively.
---
This video is based on the question https://stackoverflow.com/q/71458469/ asked by the user 'Johnson' ( https://stackoverflow.com/u/14722762/ ) and on the answer https://stackoverflow.com/a/71459863/ provided by the user 'Wernfried Domscheit' ( https://stackoverflow.com/u/3027266/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Why Mongo Auto Restart after Shutdown

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Why Does MongoDB Automatically Restart After Shutdown?

If you've ever tried to shut down your MongoDB process on a Linux server using commands like mongod.sh stop or mongo --shutdown and encountered an unexpected restart, you're not alone. This issue can be perplexing, especially when everything seems to be running smoothly otherwise. In this guide, we will delve into the details of why this happens and how you can manage your MongoDB service to prevent automatic restarts after a shutdown.

The Problem: Unexpected MongoDB Restart

Observing the Restart

In your case, even though the logs indicate that MongoDB is shutting down with the message shutting down with code:0, you then see a subsequent line that states **** SERVER RESTARTED ****. This can lead to confusion because, after attempting to stop the service, it seems to initiate another process which is not the expected behavior.

Variable Behavior Across Instances

You also mentioned that other instances of MongoDB under similar conditions shut down successfully with just one line of log output concerning the server restart. The inconsistency raises questions about the underlying configuration or service management setup across different systems.

The Solution: Managing MongoDB as a Service

Understanding MongoDB Installation

The key point to remember is that if MongoDB is installed as a service (which is common on Linux systems), it will have certain behaviors linked to service management mechanisms like systemd. This service management configuration dictates how your MongoDB instance behaves on shutdown or restart commands.

Steps to Control MongoDB Restarts

If you want to prevent MongoDB from automatically restarting, you need to manage it using systemctl. Here are the steps to do that effectively:

Stopping the MongoDB Service: To stop the MongoDB instance gracefully, use the following command:

[[See Video to Reveal this Text or Code Snippet]]

This command will halt the MongoDB service and should prevent it from logging a restart unless configured otherwise.

Disabling Automatic Restart: If your server is set to automatically restart MongoDB, you can disable this feature with the following command:

[[See Video to Reveal this Text or Code Snippet]]

By doing this, you are telling the Linux operating system not to automatically start the MongoDB service on boot or reopen if it crashes.

Ensuring Proper Shutdown

When shutting down MongoDB, always check that there are no residual processes running that could interfere with the shutdown. Additionally, regularly check your system logs for unusual entries or configurations that could affect the service management processes.

Conclusion

Dealing with automatic service restarts can be frustrating, but understanding how MongoDB operates as a service allows for better control over its behavior. By utilizing systemctl to stop and disable the automatic restart function, you can ensure a quieter and more controlled environment for your MongoDB databases.

Keep in mind these commands could affect functionality. Make sure to reassess your requirements for data persistence and service availability after making changes.

Now that you have a clearer understanding of controlling MongoDB restarts, you should be able to manage your deployments more effectively. If you have further questions or additional configurations to handle, feel free to reach out or consult the MongoDB documentation for more insights.