View the locality change history

This topic describes how to query the locality change history from the DBA_OB_TENANT_JOBS view.

For more information about the DBA_OB_TENANT_JOBS view, see DBA_OB_TENANT_JOBS.

Procedure

1. Log in to the sys tenant of the cluster as the root user.

   obclient -h172.30.xxx.xxx -P2883 -uroot@sys#obdemo -pxxxx -A
   

2. Access the database named oceanbase.

   obclient(root@sys)[(none)]> USE oceanbase;
   

3. View locality change jobs.

   • View the execution status of locality change jobs.

     obclient(root@sys)[oceanbase]> SELECT * FROM oceanbase.DBA_OB_TENANT_JOBS WHERE JOB_TYPE = 'ALTER_TENANT_LOCALITY';
     

     The query results are as follows:

     +--------+-----------------------+------------+-------------+----------+----------------------------+----------------------------+-----------+------------------------------------------------------------------------------+---------------------------------------------+----------------+-------------+
     | JOB_ID | JOB_TYPE              | JOB_STATUS | RESULT_CODE | PROGRESS | START_TIME                 | MODIFY_TIME                | TENANT_ID | SQL_TEXT                                                                     | EXTRA_INFO                                  | RS_SVR_IP      | RS_SVR_PORT |
     +--------+-----------------------+------------+-------------+----------+----------------------------+----------------------------+-----------+------------------------------------------------------------------------------+---------------------------------------------+----------------+-------------+
     |      1 | ALTER_TENANT_LOCALITY | SUCCESS    |           0 |      100 | 2023-01-05 19:33:46.730319 | 2023-01-05 19:33:46.920111 |      1002 | ALTER TENANT mysql001 locality='FULL{1}@zone1, FULL{1}@zone2'                | FULL{1}@zone1, FULL{1}@zone2, FULL{1}@zone3 | xx.xx.xx.206   |        2882 |
     |      2 | ALTER_TENANT_LOCALITY | SUCCESS    |           0 |      100 | 2023-01-05 19:38:38.416011 | 2023-01-05 19:40:11.019113 |      1002 | ALTER TENANT mysql001 locality='FULL{1}@zone1, FULL{1}@zone2, FULL{1}@zone3' | FULL{1}@zone1, FULL{1}@zone2                | xx.xx.xx.207   |        2882 |
     |      3 | ALTER_TENANT_LOCALITY | SUCCESS    |           0 |      100 | 2023-01-06 14:37:01.569689 | 2023-01-06 14:37:01.726090 |      1002 | ALTER TENANT mysql001 locality="FULL{1}@zone1, FULL{1}@zone2"                | FULL{1}@zone1, FULL{1}@zone2, FULL{1}@zone3 | xx.xx.xx.208   |        2882 |
     |      4 | ALTER_TENANT_LOCALITY | SUCCESS    |           0 |      100 | 2023-01-06 14:39:56.377599 | 2023-01-06 14:40:57.874498 |      1002 | ALTER TENANT mysql001 locality="FULL{1}@zone1, FULL{1}@zone2, FULL{1}@zone3" | FULL{1}@zone1, FULL{1}@zone2                | xx.xx.xx.209   |        2882 |
     +--------+-----------------------+------------+-------------+----------+----------------------------+----------------------------+-----------+------------------------------------------------------------------------------+---------------------------------------------+----------------+-------------+
     4 rows in set
     

   • View the locality change history of a tenant.

     obclient(root@sys)[oceanbase]> SELECT * FROM oceanbase.DBA_OB_TENANT_JOBS WHERE JOB_TYPE = 'ALTER_TENANT_LOCALITY' AND tenant_id = 1002 ORDER BY START_TIME DESC LIMIT 10;
     

     The query results are as follows:

     +--------+-----------------------+------------+-------------+----------+----------------------------+----------------------------+-----------+------------------------------------------------------------------------------+---------------------------------------------+----------------+-------------+
     | JOB_ID | JOB_TYPE              | JOB_STATUS | RESULT_CODE | PROGRESS | START_TIME                 | MODIFY_TIME                | TENANT_ID | SQL_TEXT                                                                     | EXTRA_INFO                                  | RS_SVR_IP      | RS_SVR_PORT |
     +--------+-----------------------+------------+-------------+----------+----------------------------+----------------------------+-----------+------------------------------------------------------------------------------+---------------------------------------------+----------------+-------------+
     |      4 | ALTER_TENANT_LOCALITY | SUCCESS    |           0 |      100 | 2023-01-06 14:39:56.377599 | 2023-01-06 14:40:57.874498 |      1002 | ALTER TENANT mysql001 locality="FULL{1}@zone1, FULL{1}@zone2, FULL{1}@zone3" | FULL{1}@zone1, FULL{1}@zone2                | xx.xx.xx.209   |        2882 |
     |      3 | ALTER_TENANT_LOCALITY | SUCCESS    |           0 |      100 | 2023-01-06 14:37:01.569689 | 2023-01-06 14:37:01.726090 |      1002 | ALTER TENANT mysql001 locality="FULL{1}@zone1, FULL{1}@zone2"                | FULL{1}@zone1, FULL{1}@zone2, FULL{1}@zone3 | xx.xx.xx.206   |        2882 |
     |      2 | ALTER_TENANT_LOCALITY | SUCCESS    |           0 |      100 | 2023-01-05 19:38:38.416011 | 2023-01-05 19:40:11.019113 |      1002 | ALTER TENANT mysql001 locality='FULL{1}@zone1, FULL{1}@zone2, FULL{1}@zone3' | FULL{1}@zone1, FULL{1}@zone2                | xx.xx.xx.207   |        2882 |
     |      1 | ALTER_TENANT_LOCALITY | SUCCESS    |           0 |      100 | 2023-01-05 19:33:46.730319 | 2023-01-05 19:33:46.920111 |      1002 | ALTER TENANT mysql001 locality='FULL{1}@zone1, FULL{1}@zone2'                | FULL{1}@zone1, FULL{1}@zone2, FULL{1}@zone3 | xx.xx.xx.208   |        2882 |
     +--------+-----------------------+------------+-------------+----------+----------------------------+----------------------------+-----------+------------------------------------------------------------------------------+---------------------------------------------+----------------+-------------+
     4 rows in set
     

     The query results are described as follows:

     The job with the ID of 4 is used an example. The job for changing the locality of the tenant with the ID of 1002 from FULL{1}@zone1, FULL{1}@zone2 to FULL{1}@zone1, FULL{1}@zone2, FULL{1}@zone3 was created at 2023-01-06 14:39:56.377599 and was completed at 2023-01-06 14:40:57.874498.