Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-7053

WSREP_STATUS & WSREP_MEMBERSHIP I_S tables

Details

    Description

      MariaDB Galera server currently dumps many node's status and cluster membership related information to the server logs. The idea behind this task is to make those information available to the user through INFORMATION_SCHEMA. Following is the sample output :

      MariaDB [test]> INSTALL PLUGIN wsrep_status SONAME 'wsrep_status.so';
      Query OK, 0 rows affected (0.03 sec)
       
      MariaDB [test]> INSTALL PLUGIN wsrep_membership SONAME 'wsrep_status.so';
      Query OK, 0 rows affected (0.16 sec)
       
      MariaDB [test]> SELECT * FROM INFORMATION_SCHEMA.WSREP_STATUS;
      +------------+-------------+----------------+--------------+--------------------------------------+---------------------+-----------------+-----+------------------+
      | NODE_INDEX | NODE_STATUS | CLUSTER_STATUS | CLUSTER_SIZE | CLUSTER_STATE_UUID                   | CLUSTER_STATE_SEQNO | CLUSTER_CONF_ID | GAP | PROTOCOL_VERSION |
      +------------+-------------+----------------+--------------+--------------------------------------+---------------------+-----------------+-----+------------------+
      |          0 | Synced      | Primary        |            3 | 00b0fbad-6e84-11e4-8a8b-376f19ce8ee7 |                   2 |               3 | NO  |                3 |
      +------------+-------------+----------------+--------------+--------------------------------------+---------------------+-----------------+-----+------------------+
      1 row in set (0.00 sec)
       
      MariaDB [test]> SELECT * FROM INFORMATION_SCHEMA.WSREP_MEMBERSHIP;
      +-------+--------------------------------------+-------+-----------------+
      | INDEX | UUID                                 | NAME  | ADDRESS         |
      +-------+--------------------------------------+-------+-----------------+
      |     0 | 46da96e3-6e9e-11e4-95a2-f609aa5444b3 | node1 | 10.0.2.15:16000 |
      |     1 | 5f6bc72a-6e9e-11e4-84ed-57ec6780a3d3 | node2 | 10.0.2.15:16001 |
      |     2 | 7473fd75-6e9e-11e4-91de-0b541ad91bd0 | node3 | 10.0.2.15:16002 |
      +-------+--------------------------------------+-------+-----------------+
      3 rows in set (0.00 sec)
       

      Attachments

        Activity

          nirbhay_c Nirbhay Choubey (Inactive) created issue -
          nirbhay_c Nirbhay Choubey (Inactive) made changes -
          Field Original Value New Value
          Assignee Nirbhay Choubey [ nirbhay_c ]
          nirbhay_c Nirbhay Choubey (Inactive) made changes -
          Status Open [ 1 ] In Progress [ 3 ]
          nirbhay_c Nirbhay Choubey (Inactive) made changes -
          Assignee Nirbhay Choubey [ nirbhay_c ] Jan Lindström [ jplindst ]
          Status In Progress [ 3 ] In Review [ 10002 ]
          jplindst Jan Lindström (Inactive) made changes -
          Assignee Jan Lindström [ jplindst ] Nirbhay Choubey [ nirbhay_c ]
          Status In Review [ 10002 ] Stalled [ 10000 ]
          nirbhay_c Nirbhay Choubey (Inactive) made changes -
          Description MariaDB Galera server currently dumps many node's status and cluster membership related information to the server logs. The idea behind this task is to make those information available to the user through INFORMATION_SCHEMA. Following is the sample output :

          {code}
          MariaDB [test]> INSTALL PLUGIN wsrep_status SONAME 'wsrep_status.so';
          Query OK, 0 rows affected (0.03 sec)

          MariaDB [test]> INSTALL PLUGIN wsrep_membership SONAME 'wsrep_status.so';
          Query OK, 0 rows affected (0.16 sec)

          MariaDB [test]> SELECT * FROM INFORMATION_SCHEMA.WSREP_STATUS;
          +------------+-------------+--------------+--------------------------------------+---------+-----+------------------+
          | NODE_INDEX | NODE_STATUS | CLUSTER_SIZE | CLUSTER_UUID | PRIMARY | GAP | PROTOCOL_VERSION |
          +------------+-------------+--------------+--------------------------------------+---------+-----+------------------+
          | 0 | SYNCED | 3 | 027f4cd1-66ec-11e4-8c43-6fcee8d9a95c | YES | NO | 3 |
          +------------+-------------+--------------+--------------------------------------+---------+-----+------------------+
          1 row in set (0.00 sec)

          MariaDB [test]> SELECT * FROM INFORMATION_SCHEMA.WSREP_MEMBERSHIP;
          +-------+--------------------------------------+-------+-----------------+
          | INDEX | UUID | NAME | ADDRESS |
          +-------+--------------------------------------+-------+-----------------+
          | 0 | 42f38747-66fd-11e4-b2a1-5a3d62825f3a | node1 | 10.0.2.15:16000 |
          | 1 | 4d930d1a-66fd-11e4-ae81-1f2c105e7686 | node2 | 10.0.2.15:16001 |
          | 2 | 55f3344d-66fd-11e4-94a9-efb9e4cb33bc | node3 | 10.0.2.15:16002 |
          +-------+--------------------------------------+-------+-----------------+
          3 rows in set (0.00 sec)
          {code}
          MariaDB Galera server currently dumps many node's status and cluster membership related information to the server logs. The idea behind this task is to make those information available to the user through INFORMATION_SCHEMA. Following is the sample output :

          {code}
          MariaDB [test]> INSTALL PLUGIN wsrep_status SONAME 'wsrep_status.so';
          Query OK, 0 rows affected (0.03 sec)

          MariaDB [test]> INSTALL PLUGIN wsrep_membership SONAME 'wsrep_status.so';
          Query OK, 0 rows affected (0.16 sec)

          MariaDB [test]> SELECT * FROM INFORMATION_SCHEMA.WSREP_STATUS;
          +------------+-------------+----------------+--------------+--------------------------------------+---------------------+-----------------+-----+------------------+
          | NODE_INDEX | NODE_STATUS | CLUSTER_STATUS | CLUSTER_SIZE | CLUSTER_STATE_UUID | CLUSTER_STATE_SEQNO | CLUSTER_CONF_ID | GAP | PROTOCOL_VERSION |
          +------------+-------------+----------------+--------------+--------------------------------------+---------------------+-----------------+-----+------------------+
          | 0 | Synced | Primary | 3 | 00b0fbad-6e84-11e4-8a8b-376f19ce8ee7 | 2 | 3 | NO | 3 |
          +------------+-------------+----------------+--------------+--------------------------------------+---------------------+-----------------+-----+------------------+
          1 row in set (0.00 sec)

          MariaDB [test]> SELECT * FROM INFORMATION_SCHEMA.WSREP_MEMBERSHIP;
          +-------+--------------------------------------+-------+-----------------+
          | INDEX | UUID | NAME | ADDRESS |
          +-------+--------------------------------------+-------+-----------------+
          | 0 | 46da96e3-6e9e-11e4-95a2-f609aa5444b3 | node1 | 10.0.2.15:16000 |
          | 1 | 5f6bc72a-6e9e-11e4-84ed-57ec6780a3d3 | node2 | 10.0.2.15:16001 |
          | 2 | 7473fd75-6e9e-11e4-91de-0b541ad91bd0 | node3 | 10.0.2.15:16002 |
          +-------+--------------------------------------+-------+-----------------+
          3 rows in set (0.00 sec)

          {code}
          nirbhay_c Nirbhay Choubey (Inactive) made changes -
          Resolution Fixed [ 1 ]
          Status Stalled [ 10000 ] Closed [ 6 ]
          ratzpo Rasmus Johansson (Inactive) made changes -
          Workflow MariaDB v2 [ 58323 ] MariaDB v3 [ 63601 ]
          serg Sergei Golubchik made changes -
          Workflow MariaDB v3 [ 63601 ] MariaDB v4 [ 132453 ]

          People

            nirbhay_c Nirbhay Choubey (Inactive)
            nirbhay_c Nirbhay Choubey (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 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.