Display Cluster States

Follow this procedure to determine current state information for active and standby clusters. The information displayed includes the ID, IP address, role, and state of each server or pod in the local engine, and the state of any peer clusters.

About this task

You can perform this procedure on any server or pod running in an engine. Values for the engine on which the script is run are displayed under Cluster Stats, and values for any peer engines are displayed under Peer Cluster Stats. The information returned by this script is a snapshot of the cluster state at the time the script runs.

Procedure

Run the following command to display cluster-level information for the local cluster:
kubectl exec -it engine_pod_name -n matrixx -- bash --login -c"print_blade_stats.py - C"

Results

Information like the following is displayed:
print_blade_stats.py -C -e 1 -c 2 -b 1
----------------------------------------------------------------
blade - 1:3:1 , version - 5081

time - Mon 2018-10-08T09:03:57
----------------------------------------------------------------


Cluster Stats
-------------
Node   Cluster        Service     Node  Mgmt      
  Id  LeaderId           Role    State  IP Address
========================================================
   1         1  checkpointing   active  127.0.0.1      

(On a standby processing blade the first time it is active)
Peer Cluster Stats
------------------
System Peer
Engine Cluster Cluster Schema    Cluster
    Id      Id   State Version     FQ Id   Cluster Up Time   Cluster Active Time
================================================================================================== 
     1       1 active    5110        0:0        2019-04-29           T23:12:57 0

(On standby processing blade which has been active)
Peer Cluster Stats
------------------
System Peer
Engine Cluster Cluster  Schema    Cluster
    Id      Id   State Version      FQ Id   Cluster Up Time     Cluster Active Time
==================================================================================================
     1       1  active    5110        0:0  2019-04-29T23:12:57    2019-04-27T07:01:12

Peer Cluster Stats
------------------
                                System     Peer
Engine  Cluster       Cluster   Schema  Cluster
    Id       Id         State  Version    FQ Id
===============================================
     1        1        active     5081      0:0


Processing Cluster Stats
------------------------
                                System     Peer
Engine  Cluster       Cluster   Schema  Cluster
    Id       Id         State  Version    FQ Id
===============================================
     1        3        active     5081      0:0
In this example, the Node State of all servers or pods is active, which means they are ready to process network traffic because they are in the active cluster. The peer cluster stats show that there are three engines in the domain, and their cluster states are active, standby, and standby. The Peer Cluster FQ ID lists the cluster that each cluster is supporting (receiving transactions from). Because cluster 1:1 is active, its peer cluster is 0:0 (none) because it is not replaying transactions.