mongocli ops-manager cluster startup
The cluster startup
command starts the replica set
mongod
processes for the specified cluster in the specified
Ops Manager
project. The command prompts you to confirm the
operation when you run the command without the
--force
option. You can also restart the mongod process from the
Ops Manager
UI.
Syntax
mongocli ops-manager|om cluster startup <cluster-name> [ --force ] [ --output|-o <output-format> ] [ --profile|-P <profile-name> ] [ --projectId <project-ID> ]
Note
Use -h
or --help
to view the command-line help for
this command.
Options
Option | Type | Description | Required? |
---|---|---|---|
<cluster-name> | string | Name of the cluster. | yes |
--force | Flag that indicates that the replica set mongod processes can be
started without prompting for confirmation. | no | |
--output , -o | string | Command output format. Valid values are:
If omitted, the command returns output in the default format. | no |
--profile , -P | string | Name of the profile where the public and private
keys for the project are set. If omitted, uses the
default profile. To learn more about creating a
profile, see Configure the MongoDB CLI. | no |
--projectId | string | Unique identifier of the project. If omitted, uses the project ID in the profile or environment variable. | no |
Output
The command prints output similar to the following to the terminal if the command succeeds. If the command prints errors, see Troubleshooting for recommended solutions.
Changes are being applied, please check http://<hostname>:<port>/v2/<projectID>#deployment/topology for status
where:
<hostname>:<port>
is theOps Manager
base URL.<projectID>
is the unique identifier of the project that contains the cluster to start.
Examples
The following examples show the different ways to run the command.
Example 1
The following mongocli om cluster startup
command
prompts for confirmation before starting the the replica set
mongod
processes for the cluster named myCluster
in the specified
project. It uses the default profile to access the
specified project.
mongocli om cluster startup myCluster --projectId 5e2dec2131cd7c007880b05e Are you sure you want to startup: myCluster Yes
Example 2
The following mongocli ops-manager cluster startup
command
does not prompt for confirmation before starting the replica set
mongod
processes for the cluster named myCluster
in the specified
project. It uses the default profile for accessing the specified project.
mongocli ops-manager cluster startup myCluster --projectId 5e2dec2131cd7c007880b05e --force
Output
The Example 1 and Example 2 commands print the following to the terminal:
Changes are being applied, please check http://localhost:30700/v2/5e2dec2131cd7c007880b05e#deployment/topology for status