Obtaining Database Status Information Using NuoDB Manager

NuoDB Manager provides several commands that you can use to obtain status information:

The example below shows a database that is up and running. Its process requirements status is MET, its client availability status is ACTIVE and its dominant process status is RUNNING.

nuodb [domain] > show domain summary 
Hosts:
[broker] * ec2-54-200-117-181.us-west-2.compute.amazonaws.com/172.31.5.193:48004 (us-west-2)
[broker] ip-172-31-14-151/52.10.63.144:48004 (us-west-2)
[broker] ip-172-31-2-230/54.148.240.227:48004 (us-west-2)
 
Database: test, template [Minimally Redundant] MET, processes [2 TE, 2 SM], ACTIVE
[SM] ip-172-31-5-193/54.200.117.181:48005 (us-west-2) [ pid = 2742 ] [ nodeId = 1 ] RUNNING
[TE] ip-172-31-5-193/54.200.117.181:48006 (us-west-2) [ pid = 2760 ] [ nodeId = 2 ] RUNNING
[SM] ip-172-31-14-151/52.10.63.144:48005 (us-west-2) [ pid = 32476 ] [ nodeId = 3 ] RUNNING
[TE] ip-172-31-2-230/54.148.240.227:48005 (us-west-2) [ pid = 3785 ] [ nodeId = 6 ] RUNNING
 
nuodb [domain] > show database config
Database: test
Database: test, ACTIVE, Status=RUNNING, template [Minimally Redundant]
  Variables: {HOST=2f19762c-0e50-4ec3-b252-bb3a9dccaef4, REGION=us-west-2}
  Options: {}
  Default Options: { "commit": "${COMMIT:remote:1}","backoff.reqMinUptime":"30000","hostLimit":"${HOST_LIMIT:false}"}
  Process group options:
  Process group tag constraints:
  Archive Locations:
    ip-172-31-14-151/52.10.63.144:48004, requirements: SMs, region: us-west-2:
      archive: /var/opt/nuodb/production-archives/test
      journal-dir: /var/opt/nuodb/production-archives/test
    ec2-54-200-117-181.us-west-2.compute.amazonaws.com/172.31.5.193:48004, requirements: SMs, region: us-west-2:
      archive: /var/opt/nuodb/production-archives/test
      journal-dir: /var/opt/nuodb/production-archives/test
  Minimally Redundant MET