Deploys a new MongoDB Replica Set. The database cluster will be automatically added to ClusterControl once deployed. A minimum of three nodes (including mongo arbiter) is recommended.
It is possible to deploy only 2 MongoDB nodes (without an arbiter). The caveat of this approach is no automatic failover. If the primary node goes down then manual failover is required to make the other server runs as primary. Automatic failover works fine with 3 nodes and more.
General & SSH Settings
Specify root if you have root credentials.
If you use sudo to execute system commands, specify the name that you wish to use here. The user must exist on all nodes. See Operating System User.
SSH Key Path
Specify the full path of SSH key (the key must exist in the ClusterControl node) that will be used by SSH User to perform passwordless SSH. See Passwordless SSH.
If you use sudo with password, specify it here. Ignore this if SSH User is root or sudoer does not need a sudo password.
Specify the SSH port for target nodes. ClusterControl assumes SSH is running on the same port on all nodes.
Specify a name for the cluster.
Check the box if you use clean and minimal VMs. Existing MySQL dependencies will be removed. New packages will be installed and existing packages will be uninstalled when provisioning the node with the required software. – If unchecked, existing packages will not be uninstalled, and nothing will be installed. This requires that the instances have already provisioned the necessary software.
Check the box to disable the firewall (recommended).
Check the box to let ClusterControl disable AppArmor (Ubuntu) or SELinux (RedHat/CentOS) if enabled (recommended).
Location of MongoDB data directory. Default is /var/lib/mongodb.
MongoDB admin user. ClusterControl will create this user and enable authentication.
Password for MongoDB Admin User.
MongoDB server port. Default is 27017.
MongoDB configuration template file under /etc/cmon/templates or /usr/share/cmon/templates. See Base Template Files for details.
Specify the name of the replica set, similar to replication.replSetName option in MongoDB.
Use Vendor Repositories – Provision software by setting up and using the database vendor’s preferred software repository. ClusterControl will always install the latest version of what is provided by the database vendor repository.
Do Not Setup Vendor Repositories – Provision software by using repositories already set up on the nodes. The User has to set up the software repository manually on each database node and ClusterControl will use this repository for deployment. This is good if the database nodes are running without internet connections.
Use Mirrored Repositories – Create and mirror the current database vendor’s repository and then deploy using the local mirrored repository. This is a preferred option when you have to scale the MongoDB in the future, to ensure the newly provisioned node will always have the same version as the rest of the members.
Specify the IP address or hostname of the MongoDB nodes. A minimum of three nodes is required.