After a partition balancing task is triggered in a scheduled manner, you can view the triggering history of the scheduled partition balancing task through a view.
View the triggering history of the scheduled partition balancing task in the sys tenant
Log in to the
systenant of the cluster as therootuser.Here is an example of the connection command. Replace the parameters with those in your actual environment.
obclient -h10.xx.xx.xx -P2883 -uroot@sys#obdemo -p***** -AExecute the following statement to view the history of scheduled runs of the scheduled partition balancing task in the specified tenant.
The
CDB_SCHEDULER_JOB_RUN_DETAILSview displays the run records of the SCHEDULED_TRIGGER_PARTITION_BALANCE job of all tenants.obclient [oceanbase]> SELECT * FROM oceanbase.CDB_SCHEDULER_JOB_RUN_DETAILS WHERE TENANT_ID = 1002 AND JOB_NAME = 'SCHEDULED_TRIGGER_PARTITION_BALANCE'\GThe query result is as follows:
*************************** 1. row *************************** LOG_ID: 0 LOG_DATE: NULL OWNER: NULL JOB_NAME: SCHEDULED_TRIGGER_PARTITION_BALANCE JOB_SUBNAME: NULL STATUS: NULL CODE: -7124 REQ_START_DATE: NULL ACTUAL_START_DATE: NULL RUN_DURATION: NULL INSTANCE_ID: NULL SESSION_ID: NULL SLAVE_PID: NULL CPU_USED: NULL CREDENTIAL_OWNER: NULL CREDENTIAL_NAME: NULL DESTINATION_OWNER: NULL DESTINATION: NULL MESSAGE: partitions are already balanced, no need to trigger partition balance TENANT_ID: 1002 JOB: 11 TIME: 2024-06-14 00:00:00.124110 JOB_CLASS: DEFAULT_JOB_CLASS GMT_CREATE: 2024-06-14 00:00:00.124110 GMT_MODIFIED: 2024-06-14 00:00:00.124110 *************************** 2. row *************************** LOG_ID: 0 LOG_DATE: NULL OWNER: NULL JOB_NAME: SCHEDULED_TRIGGER_PARTITION_BALANCE JOB_SUBNAME: NULL STATUS: NULL CODE: 0 REQ_START_DATE: NULL ACTUAL_START_DATE: NULL RUN_DURATION: NULL INSTANCE_ID: NULL SESSION_ID: NULL SLAVE_PID: NULL CPU_USED: NULL CREDENTIAL_OWNER: NULL CREDENTIAL_NAME: NULL DESTINATION_OWNER: NULL DESTINATION: NULL MESSAGE: SUCCESS TENANT_ID: 1002 JOB: 11 TIME: 2024-06-14 17:00:00.143494 JOB_CLASS: DEFAULT_JOB_CLASS GMT_CREATE: 2024-06-14 17:00:00.143494 GMT_MODIFIED: 2024-06-14 17:00:00.143494 2 rows in setFor more information about the fields in the
CDB_SCHEDULER_JOB_RUN_DETAILSview, see CDB_SCHEDULER_JOB_RUN_DETAILS.
View the triggering history of the scheduled partition balancing task in a user tenant
Log in to a MySQL tenant or an Oracle tenant of the cluster as the tenant administrator of the user tenant.
Here is an example of the connection command. Replace the parameters with those in your actual environment.
obclient -h10.xx.xx.xx -P2883 -uroot@mysql_tenant#obdemo -p***** -AExecute the following statement to view the history of scheduled runs of the scheduled partition balancing task in the current tenant.
The
DBA_SCHEDULER_JOB_RUN_DETAILSview displays the run records of the SCHEDULED_TRIGGER_PARTITION_BALANCE job in the current tenant.MySQL-compatible modeOracle-compatible modeThe statement is as follows:
obclient [oceanbase]> SELECT * FROM oceanbase.DBA_SCHEDULER_JOB_RUN_DETAILS WHERE JOB_NAME = 'SCHEDULED_TRIGGER_PARTITION_BALANCE'\GThe statement is as follows:
obclient [SYS]> SELECT * FROM SYS.DBA_SCHEDULER_JOB_RUN_DETAILS WHERE JOB_NAME = 'SCHEDULED_TRIGGER_PARTITION_BALANCE'\GThe query result is as follows:
*************************** 1. row *************************** LOG_ID: 0 LOG_DATE: NULL OWNER: NULL JOB_NAME: SCHEDULED_TRIGGER_PARTITION_BALANCE JOB_SUBNAME: NULL STATUS: NULL CODE: -7124 REQ_START_DATE: NULL ACTUAL_START_DATE: NULL RUN_DURATION: NULL INSTANCE_ID: NULL SESSION_ID: NULL SLAVE_PID: NULL CPU_USED: NULL CREDENTIAL_OWNER: NULL CREDENTIAL_NAME: NULL DESTINATION_OWNER: NULL DESTINATION: NULL MESSAGE: partitions are already balanced, no need to trigger partition balance JOB: 11 TIME: 2024-06-14 00:00:00.124110 JOB_CLASS: DEFAULT_JOB_CLASS GMT_CREATE: 2024-06-14 00:00:00.124110 GMT_MODIFIED: 2024-06-14 00:00:00.124110 *************************** 2. row *************************** LOG_ID: 0 LOG_DATE: NULL OWNER: NULL JOB_NAME: SCHEDULED_TRIGGER_PARTITION_BALANCE JOB_SUBNAME: NULL STATUS: NULL CODE: 0 REQ_START_DATE: NULL ACTUAL_START_DATE: NULL RUN_DURATION: NULL INSTANCE_ID: NULL SESSION_ID: NULL SLAVE_PID: NULL CPU_USED: NULL CREDENTIAL_OWNER: NULL CREDENTIAL_NAME: NULL DESTINATION_OWNER: NULL DESTINATION: NULL MESSAGE: SUCCESS JOB: 11 TIME: 2024-06-14 17:00:00.143494 JOB_CLASS: DEFAULT_JOB_CLASS GMT_CREATE: 2024-06-14 17:00:00.143494 GMT_MODIFIED: 2024-06-14 17:00:00.143494 2 rows in setFor more information about the fields in the
DBA_SCHEDULER_JOB_RUN_DETAILSview, see DBA_SCHEDULER_JOB_RUN_DETAILS.