Quickly deploy MongoDB on Compute Engine

The Google Developers Console provides a simple interface that you can use to quickly configure your MongoDB cluster.

1. In the MongoDB click-to-deploy page in the Google Developers Console , specify your configuration settings or use the default values.

   Configuration option details

   Field	Default	Description
   Replica set name	rs0	The MongoDB replica set that each node will join.
   Server node name prefix	mongo-db	Each server node will be given a unique instance name in the form prefix- xxxx where the xxxx is a random four character string.
   Server node machine type	n1-highmem-4	The Compute Engine machine type for the server nodes. MongoDB works best when the active working data set can be kept in memory. Learn more about choosing the machine types for your configuration.
   Arbiter node machine type	f1-micro	The Compute Engine machine type for the arbiter nodes.
   Advanced options
   Replica set key		The MongoDB replica set key for members of the replica set to authenticate to each other.
   Network name	default	Existing Compute Engine network that instances will belong to.
   Deployment coordinator name prefix	mongo-coord	The deployment coordinator node will be given a unique instances name in the form prefix- xxxx where xxxx is a random four character string.
   Deployment coordinator machine type	n1-standard-1	The Compute Engine machine type for the deployment coordinator node.
   Server node count	2	The number of server nodes to create. The first node (alphabetically) will be the intial MongoDB primary node.
   Server node disk size	1000GB	Size of the persistent disk data volumes. A separate disk will be created and attached for each server node.
   Arbiter node count	1	The number of arbiter nodes to create. Use arbiter nodes to ensure an odd number of voting members in the replica set.
   Zone	us-central1-a	The Compute Engine zone in which instances will be created.

   If you are doing performance testing, choose your data disk size and machine types appropriately. For more information, see performance considerations and tuning .

2. Click Deploy cluster

3. Optional: Install the Cloud SDK to be able to connect to your MongoDB instances when deployment finishes.

The deployment can take a few minutes, when it finishes, you are provided with a command that you can run to connect to the primary MongoDB server instance by using the gcutil ssh command. You can connect to your instances using ssh to further configure the instances or to perform other tasks such as testing.

When you are finished with the cluster, you can click the Delete Cluster button in the Developers Console to stop all instances and destroy the associated data disks.

Next steps

You might also want to learn about how the MongoDB cluster was deployed. You can learn how Deployment Manager was used and extend that knowledge to your own projects.

Next: Learn how MongoDB was deployed

Troubleshooting

If a deployment fails to complete successfully, check the error message in the Developers Console. If the problem is a CPU quota issue or other problem that you can correct, delete the deployment, correct the problem, and try again.

If the error message on the Developers Console does not provide sufficient detail about the failure, check the Deployment Manager output on the virtual machine instances that were launched. On each instance, there will be a directory /gagent/metaOutput with a set of numbered files: stdoutN.txt , stderrN.txt , exitcodeN.txt . Each set of such files corresponds to the sequenced command that was executed by Deployment Manager for your deployment on that instance.

To get a list of your compute engine instances, check the Compute Engine list of virtual machine instances in the Developers Console or run the following command:

 $ gcloud compute instances list -l

To ssh to an instance:

 $ gcloud compute ssh <instance> --zone=<zone>

If you have problems that you cannot resolve or have questions head to Stack Overflow .