Uploaded image for project: 'MariaDB ColumnStore'
  1. MariaDB ColumnStore
  2. MCOL-4298

CMAPI Status less usable than legacy ma getsystemstatus command

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Won't Do
    • Affects Version/s: None
    • Fix Version/s: N/A
    • Component/s: N/A
    • Labels:
      None

      Description

      Usage

      The new CMAPI command is much lengthier than the legacy ma getsystemstatus command and now requires an API key. This makes it far more difficult to utilize when troubleshooting an issue.

      New:

      curl -s https://127.0.0.1:8640/cmapi/0.4.0/cluster/status --header 'Content-Type:application/json' --header 'x-api-key:somekey123' -k | jq .

      Legacy:

      ma getsystemstatus

      Information

      It also contains less information in a more difficult to parse format

      CMAPI Status

      {
      "timestamp": "2020-09-05 04:32:29.958394",
      "ip-10-0-10-94.us-west-1.compute.internal": {
      "timestamp": "2020-09-05 04:32:29.964061",
      "uptime": 10600,
      "dbrm_mode": "master",
      "cluster_mode": "readwrite",
      "dbroots": [],
      "module_id": 1,
      "services": [

      { "name": "workernode", "pid": 22906 }

      ,

      { "name": "controllernode", "pid": 22964 }

      ,

      { "name": "PrimProc", "pid": 22973 }

      ,

      { "name": "ExeMgr", "pid": 23008 }

      ,

      { "name": "WriteEngine", "pid": 23017 }

      ,

      { "name": "DMLProc", "pid": 23053 }

      ,

      { "name": "DDLProc", "pid": 23054 }

      ]
      },
      "ip-10-0-11-168.us-west-1.compute.internal": {
      "timestamp": "2020-09-05 04:32:30.009049",
      "uptime": 10684,
      "dbrm_mode": "slave",
      "cluster_mode": "readonly",
      "dbroots": [],
      "module_id": 2,
      "services": [

      { "name": "workernode", "pid": 18753 }

      ,

      { "name": "PrimProc", "pid": 18761 }

      ,

      { "name": "ExeMgr", "pid": 18801 }

      ,

      { "name": "WriteEngine", "pid": 18810 }

      ]
      },
      "ip-10-0-10-201.us-west-1.compute.internal": {
      "timestamp": "2020-09-05 04:32:30.055930",
      "uptime": 691,
      "dbrm_mode": "slave",
      "cluster_mode": "readonly",
      "dbroots": [],
      "module_id": 3,
      "services": [

      { "name": "workernode", "pid": 3708 }

      ,

      { "name": "PrimProc", "pid": 3718 }

      ,

      { "name": "ExeMgr", "pid": 3760 }

      ,

      { "name": "WriteEngine", "pid": 3769 }

      ]
      },
      "num_nodes": 3
      }

      Legacy:

      Short Version:

      Gives all nodes and their current status clearly. It also tells which one is the parent node and if it is replicating and distributed.

      PROD-X-CS-PM1~[mariadbadmin]$ ma getsystemstatus
      getsystemstatus Tue Sep 8 17:55:10 2020

      System columnstore-1

      System and Module statuses

      Component Status Last Status Change
      ------------ -------------------------- ------------------------
      System ACTIVE Fri Aug 28 21:24:28 2020

      Module um1 ACTIVE Fri Aug 28 21:24:22 2020
      Module pm1 ACTIVE Fri Aug 28 21:24:05 2020
      Module pm2 ACTIVE Fri Aug 28 21:24:11 2020

      Active Parent OAM Performance Module is 'pm1'
      MariaDB ColumnStore Replication Feature is enabled
      MariaDB ColumnStore set for Distributed Install

      Detailed Version:

      PROD-X-CS-PM1~[mariadbadmin]$ ma getsysteminfo
      getsysteminfo Tue Sep 8 17:56:14 2020

      System columnstore-1

      System and Module statuses

      Component Status Last Status Change
      ------------ -------------------------- ------------------------
      System ACTIVE Fri Aug 28 21:24:28 2020

      Module um1 ACTIVE Fri Aug 28 21:24:22 2020
      Module pm1 ACTIVE Fri Aug 28 21:24:05 2020
      Module pm2 ACTIVE Fri Aug 28 21:24:11 2020

      Active Parent OAM Performance Module is 'pm1'
      MariaDB ColumnStore Replication Feature is enabled
      MariaDB ColumnStore set for Distributed Install

      MariaDB ColumnStore Process statuses

      Process Module Status Last Status Change Process ID
      ------------------ ------ --------------- ------------------------ ----------
      ProcessMonitor um1 ACTIVE Fri Aug 28 21:23:34 2020 1366
      ServerMonitor um1 ACTIVE Fri Aug 28 21:23:59 2020 2143
      DBRMWorkerNode um1 ACTIVE Fri Aug 28 21:24:06 2020 2405
      ExeMgr um1 ACTIVE Fri Aug 28 21:24:15 2020 3305
      DDLProc um1 ACTIVE Fri Aug 28 21:24:19 2020 3362
      DMLProc um1 ACTIVE Fri Aug 28 21:24:23 2020 3408
      mysqld um1 ACTIVE Fri Aug 28 21:24:14 2020 2098

      ProcessMonitor pm1 ACTIVE Fri Aug 28 21:23:19 2020 1264
      ProcessManager pm1 ACTIVE Fri Aug 28 21:23:25 2020 1630
      DBRMControllerNode pm1 ACTIVE Fri Aug 28 21:23:59 2020 2445
      ServerMonitor pm1 ACTIVE Fri Aug 28 21:24:01 2020 2477
      DBRMWorkerNode pm1 ACTIVE Fri Aug 28 21:24:01 2020 2530
      PrimProc pm1 ACTIVE Fri Aug 28 21:24:05 2020 2618
      WriteEngineServer pm1 ACTIVE Fri Aug 28 21:24:06 2020 2646

      ProcessMonitor pm2 ACTIVE Fri Aug 28 21:23:45 2020 1274
      ProcessManager pm2 HOT_STANDBY Fri Aug 28 21:24:28 2020 1966
      DBRMControllerNode pm2 COLD_STANDBY Fri Aug 28 21:24:00 2020
      ServerMonitor pm2 ACTIVE Fri Aug 28 21:24:03 2020 1773
      DBRMWorkerNode pm2 ACTIVE Fri Aug 28 21:24:07 2020 1806
      PrimProc pm2 ACTIVE Fri Aug 28 21:24:12 2020 1823
      WriteEngineServer pm2 ACTIVE Fri Aug 28 21:24:13 2020 1833

      Active Alarm Counts: Critical = 0, Major = 0, Minor = 0, Warning = 0, Info = 0

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            nicklamb Nick (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.