INFORMATION_SCHEMA.TDSTORE_REGION_EVENT_INFO is used to query the execution status of REGION-related tasks at the TDStore layer, including create region, delete region, split region, and merge region.Field Name | Type | Description |
node_name | varchar(64) | Node name. |
job_description | text | Task description. |
ret | varchar(64) | return value of the function. |
job_id | bigint unsigned | Task ID. |
rep_group_id | bigint unsigned | RG ID. |
old_key_range_region_ids | text | Original REGION ID list. |
key_range_region_id | bigint unsigned | In the create region scenario, it represents the ID of the newly created REGION.In the split region scenario, it represents the ID of the split-generated REGION.In the merge region scenario, it represents the ID of the merged REGION. |
my_job_ret | varchar(64) | return value of the task |
report_mc_ret | varchar(64) | Reporting of the MC return value. |
event_type | varchar(64) | Task type. |
begin_time | varchar(64) | Start time of the task. |
cost_us | bigint unsigned | Task duration, in microseconds. |
detailed_info | text | Time consumption for each step of tasks and subtasks. |
tdsql>select * from TDSTORE_REGION_EVENT_INFO limit 1 \\G*************************** 1. row ***************************node_name: node-Module13-180-5-004job_description: create key range regionjob_id: 578rep_group_id: 70695old_key_range_region_ids: NULLkey_range_region_id: 569ret: 0(EC_OK)my_job_ret: 0(EC_OK)report_mc_ret: 0(EC_OK)event_type: TD_EVENT_CREATE_REGION_MAINbegin_time: 2024-11-04 20:02:02 258cost_us: 44083detailed_info: [CREATE_REGION_MAIN: <BEGIN: 2us>, <CHECK_EXIST: 2us>, <CHECK_OVERLAP: 131us>, <PREPARE: 51us>, <CHECK_READY: 0us>, <REPORT_PREPARE: 43734us>, <COMMIT: 70us>, <CLEAN_FAILED_JOB: 0us>, <END: 93us>]
Was this page helpful?
You can also Contact sales or Submit a Ticket for help.
Help us improve! Rate your documentation experience in 5 mins.
Feedback