MongoDB stands out as a dependable and effective choice for many organizations in the ever-evolving world of data management. However, as is the case with any technology, it's crucial to stay informed about best practices and effectively address any challenges that may come your way.

In this blog post, we'll take a closer look at a common issue that MongoDB users often encounter: the delay in getting started with mongosh. We'll explore this problem, its potential consequences, and the recommended solutions to ensure that your MongoDB operations run smoothly.

Let's dive into the details of this widespread problem.

Understanding the Issue

The problem centers on a significant delay, lasting approximately 2 to 3 seconds, that occurs when trying to connect to MongoDB within one of our production environments. In the context of managing databases, even a minor delay can set off a chain reaction of issues, especially in situations where quick and frequent database access is essential. This delay becomes more noticeable due to our recent shift from using the mongo package to the mongosh package, as the mongo package has been deprecated starting from version 6.0 onwards.

Production Environment Details:

• MongoDB Version: 6.0.1
• Mongosh Version: 1.5.4
• MongoDB Operates within a Docker Container.

Please note that this issue isn't limited solely to MongoDB instances running within Docker containers. It's also influenced by the version of the 'mongosh' package in use.

FYI: It's worth mentioning that such issues were observed with mongosh installations before January 9, 2023. Subsequent releases have addressed this concern, primarily focusing on improving startup times. It's important to note that Mongosh is officially supported from MongoDB version 5.0 onwards.

Resolution

The resolution involves addressing startup issues, as highlighted in the official MongoDB documentation. These issues have been successfully resolved in mongosh versions #v1.6.2 and newer.

Specific Fixes:

• mongosh version #v1.6.2 notably improves the startup time of mongosh instances.

By updating to mongosh version #v1.6.2 or later, these fixes can be applied to mitigate the prolonged startup time issue.

Upgrading the mongosh package:

Environment: Amazon Linux 2

Update the repository file

To initiate the upgrade process, start by taking your existing MongoDB repository file and make the necessary updates to match it with your specific environment.

 
vi /etc/yum.repos.d/mongodb-org-7.0.repo

[mongodb-org-7.0]
name=MongoDB Repository
baseurl=https://repo.mongodb.org/yum/amazon/$releasever/mongodb-org/7.0/$basearch/
gpgcheck=1
enabled=1
gpgkey=https://www.mongodb.org/static/pgp/server-7.0.asc
	

Install the required package

 
sudo yum install -y mongodb-mongosh
	

• Note: There's no need to uninstall the current 'mongosh' package. Executing the provided command will perform an update, effectively replacing the existing version with the new one. It's important to note that MongoDB doesn't offer support for manually installing a specific monitored version of 'mongosh'; instead, it automatically installs the latest available version.
• Note: If you're dealing with installations in various environments, you can consult the MongoDB official documentation at https://www.mongodb.com/docs/mongodb-shell/install/ for comprehensive guidance.

JustificationThe included script and output demonstrate the differences between mongosh versions 1.5.4 (/bin/mongosh) and 2.0.0 (/home/mydbops/mongosh), showcasing the improvements achieved through the upgrade.Script

 
vi mongosh_validations.sh

echo "$(date -Is)"
echo "mongosh version: $(/home/mydbops/mongosh --version)"
echo "Time Before Login: $(date +'%T+%3N')"
echo "Time After Connecting: $(/home/mydbops/mongosh --quiet --eval 'new Date()')"

echo -e "\n\n$(date -Is)"
echo "mongosh version: $(mongosh --version)"
echo "Time Before Login: $(date +'%T+%3N')"
echo "Time After Connecting: $(mongosh --quiet --eval 'new Date()')"
	

Output

 
root@ip-172-31-42-216:/home/mydbops# bash mongosh_validations.sh 
2023-09-08T12:56:41+00:00
mongosh version: 2.0.0
Time Before Login: 12:56:41+764
Time After Connecting: ISODate("2023-09-08T12:56:42.960Z")

2023-09-08T12:56:43+00:00
mongosh version: 1.5.4
Time Before Login: 12:56:45+433
Time After Connecting: ISODate("2023-09-08T12:56:47.345Z")
	

Note: The validation described above is based on our testing environment. In real-world production scenarios, connectivity experiences may differ.

Testing Environment Details

• MongoDB Version: 6.0.1
• Mongosh Version: 1.5.4
• MongoDB Operates within a Docker Container.
• Docker OS ubuntu 20.04

Reference documents:

Reference 1

Reference 2

We hope this blog helps you resolve any slow connectivity issues and ensures the seamless performance of your MongoDB environment.

Stay tuned for additional MongoDB insights and best practices! Should you have any questions or require further assistance, please don't hesitate to share them in the comments section below.