manager ​

Run operations on the manager nodes.

manager reboot [ local | remote ]
manager reset [ local | remote ]
manager resume [ local | remote ]
manager shutdown [ local | remote ]
manager standby [ local | remote ]
manager status [ all | local | remote ]

Note: The manager node where ybcli is running is considered the local node. The other manager node is considered remote. The nodes are clearly identified when you start ybcli:

Yellowbrick Data CLI v3.1.xx
Copyright (c) 2016-2019 Yellowbrick Data, Inc.
All rights reserved
-----------------------------------------
Redundant manager node detected
YBCLI is currently running on the PRIMARY manager node. 
Local manager node : yb99-mgr0 -> (PRIMARY ACTIVE)
Remote manager node: yb99-mgr1 -> (SECONDARY ACTIVE)

reboot

Reboot a manager node. For example:

YBCLI (PRIMARY)> manager reboot remote

WARNING: The local node is currently the primary
Rebooting the remote node will disable system redundancy

Are you sure you want to do this?
Type yes to continue: yes

Remote manager node
-------------------

Initiating reboot. This process can take 60 seconds

reset

Hardware reset of a manager node in the event of a system malfunction. Running manager reset on the primary manager node will be disruptive to the database and should only be used as a last resort if manager reboot is unsuccessful. For example:

YBCLI(2675) (PRIMARY - yb00-mgr1)> manager reset local

Warning: The local node is currently the primary node.
Resetting the local node initiates a system failover, causing all services to restart.
If the remote node is unavailable, resetting the local node causes a database shutdown.
Continue (yes/no)? yes
Initiating reset in 3 seconds
Manager will be reset in 3 seconds

resume

Bring a manager node that was on standby back into the HA cluster, enabling redundancy.

shutdown

Shut down one or both manager nodes. For example:

YBCLI (PRIMARY)> manager shutdown local
Warning: The local node is currently the primary node
Shutting down the local node will initiate a system fail-over
This will cause all services to restart or if the remote node is unavailable, a database shutdown
Continue (yes/no)?
...

standby

Remove a manager node from the HA cluster, disabling redundancy and putting the node on standby.

YBCLI (PRIMARY)> manager standby local

Warning: The local node is currently the primary
Enabling standby mode on the local node will initiate a system fail-over
This will cause all services to restart or if both nodes are in standby, a database shutdown

ERROR: YBCLI cannot perform a failover while connected to the floating cluster IP
To perform a cluster failover, please connect to the IP address of the current primary or secondary node

The IP addresses and hostnames of the manager nodes can be obtained using the following commands:
	health network
	config hostname get

status

Get status information about one or both of the manager nodes. For example:

YBCLI (PRIMARY)> manager status all

Host         : yb100-mgr0.yellowbrickroad.io
Uptime       : 40 days, 01:57:32
Users online : 2
CPU usage    : 0.2 %
Memory used  : 11G GiB
Memory free  : 232G GiB

Remote manager node
-------------------

Host         : yb100-mgr1.yellowbrickroad.io
Uptime       : 40 days, 02:01:34
Users online : 0
CPU usage    : 0.2 %
Memory used  : 2.8G GiB
Memory free  : 247G GiB

Parent topic:ybcli Reference