teseladb admin topology
How to use teseladb admin topology, with its options and its examples.
Usage
teseladb admin --node <addr> topology set <mongos|replicaset> [--name <set>] [--primary <host:port>]Description
Changes live how the cluster presents itself to drivers, as a mongos or as a replica set.
Options
| Option | Default | Description |
|---|---|---|
--node | 127.0.0.1:27200 | Administration port of the node being asked. |
--format | Prints the output as JSON instead of text. | |
--dbpath | Data directory of the node. In teseladb admin, the directory whose PKI provides the credentials. | |
--tlsCertificateKeyFile | the PKI ones | Certificate and key in PEM. On a node, they replace the PKI ones; in admin and mcp, they are the client's. |
--tlsCAFile | the PKI one | CA in PEM. On a node, the one that verifies client certificates; in admin and mcp, the one that signed the node certificate. |
--name | Name of the replica set the drivers see, the replicaSet= of their connection string. If you change it, the drivers set up with the old name stop using the cluster. | |
--primary | Node announced as the primary, as host:port. Without this option it is the leader of Group 0. |
Examples
Present as a replica set
Shell
teseladb admin topology set replicaset --name rs0Exit codes
0The command finished correctly.1The command failed while running; the error says why.2The command was written wrongly, with an argument missing or an unknown option.