Sample Output
You can verify that the
local cluster node has rebooted or is in the process of rebooting
in several ways:
show cluster task local
—display
tasks requested on the local node.
show cluster task current
—display
currently running tasks on the local node or the last completed
task (
controller nodes only
).
show cluster task pending
—display
tasks that are queued but have not run yet on the local node (
controller
nodes only
).
show cluster task history
—display
tasks that have been run on the local node (
controller nodes
only
).
For example, the following command shows
that two cluster node reboot tasks have completed successfully:
admin@qa15(passive-controller)>
show cluster task history
Request: reboot from qa16 (009701000044/35533) at 2017-02-17 19:21:53 UTC
Reboot requested by admin
Response: permit by qa15 at 2017-02-17 22:11:31 UTC
request not affecting healthy core server.
Progress: Wait for kv store ready for query...
KV store is ready, wait for cluster leader available...
Cluster leader is 2.2.2.16...
Checking is sysd and clusterd are alive...
Checking if cluster-mgr is ready...
Checking global-db-cluster readiness...
Stopping global-queue server and leaving cluster...
Stopping global-db servers and doing failover...
rebooting...
Finished: success at 2017-02-17 22:17:56 UTC
Request: reboot from qa16 (009701000044/35535) at 2017-02-17 22:45:50 UTC
Reboot requested by admin
Response: permit by qa15 at 2017-02-17 23:06:44 UTC
request not affecting healthy core server.
Progress: Wait for kv store ready for query...
KV store is ready, wait for cluster leader available...
Cluster leader is 2.2.2.15...
Checking is sysd and clusterd are alive...
Checking if cluster-mgr is ready...
Checking global-db-cluster readiness...
Stopping global-queue server and leaving cluster...
Stopping global-db servers and doing failover...
rebooting...
Finished: success at 2017-02-17 23:12:53 UTC