GS_WLM_OPERATOR_STATISTICS
GS_WLM_OPERATOR_STATISTICS displays the operators of the jobs that are being executed by the current user.
Name |
Type |
Description |
---|---|---|
queryid |
bigint |
Internal query_id used for statement execution |
pid |
bigint |
ID of the backend thread |
plan_node_id |
integer |
plan_node_id of the execution plan of a query |
plan_node_name |
text |
Name of the operator corresponding to plan_node_id. The maximum length of the operator name is 127 characters (excluding format characters such as spaces). |
start_time |
timestamp with time zone |
Time when the operator starts to be executed for the first time. |
duration |
bigint |
Total execution time of the operator from the start to the end, in milliseconds. |
status |
text |
Execution status of the current operator. The value can be waiting, running, or finished. |
query_dop |
integer |
DOP of the current operator |
estimated_rows |
bigint |
Number of rows estimated by the optimizer. If the number of returned estimated rows exceeds int64_max, int64_max is displayed. |
tuple_processed |
bigint |
Total number of elements returned by the current operator on all DNs. If the estimated number of returned rows exceeds int64_max, int64_max is displayed. |
min_peak_memory |
integer |
Minimum peak memory used by the current operator on all DNs. The unit is MB. |
max_peak_memory |
integer |
Maximum peak memory used by the current operator on all DNs. The unit is MB. |
average_peak_memory |
integer |
Average peak memory used by the current operator on all DNs. The unit is MB. |
memory_skew_percent |
integer |
Memory usage skew of the current operator among DNs |
min_spill_size |
integer |
Minimum logical spilled data among all DNs when a spill occurs, in MB. The default value is 0. |
max_spill_size |
integer |
Maximum logical spilled data among all DNs when a spill occurs, in MB. The default value is 0. |
average_spill_size |
integer |
Average logical spilled data among all DNs when a spill occurs, in MB. The default value is 0. |
spill_skew_percent |
integer |
DN spill skew when a spill occurs |
min_cpu_time |
bigint |
Minimum execution time of the operator on all DNs. The unit is ms. |
max_cpu_time |
bigint |
Maximum execution time of the operator on all DNs. The unit is ms. |
total_cpu_time |
bigint |
Total execution time of the operator on all DNs. The unit is ms. |
cpu_skew_percent |
integer |
Skew of the execution time among DNs. |
warning |
text |
Warning. The following warnings are displayed:
|
parent_id |
integer |
Parent node ID of the operator node. |
exec_count |
integer |
Maximum number of times that the operator node can be executed on all DNs. |
progress |
text |
Progress information of the operator. For the first operator, it is the overall progress of the job. For other operators, it is the progress of the current operator. |
min_net_size |
bigint |
Minimum network communication data volume (KB) of the operator on all DNs. It mainly applies to network operators. |
max_net_size |
bigint |
Maximum network communication data volume (KB) of the operator on all DNs. It mainly applies to network operators. |
total_net_size |
bigint |
Total network communication data volume (KB) of the operator on all DNs. It mainly applies to network operators. |
min_read_bytes |
bigint |
Minimum amount of data read by the operator from disks on all DNs. The unit is KB. |
max_read_bytes |
bigint |
Maximum amount of data read by the operator from disks on all DNs. The unit is KB. |
total_read_bytes |
bigint |
Total amount of data read by the operator from disks on all DNs, in KB. |
min_write_bytes |
bigint |
Minimum amount of data written by the operator to disks on all DNs. The unit is KB. |
max_write_bytes |
bigint |
Maximum amount of data written by the operator to disks on all DNs. The unit is KB. |
total_write_bytes |
bigint |
Total amount of data written by the operator to disks on all DNs, in KB. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot