Description
This statement is used to display information about ODP and OceanBase Database.
Syntax
SHOW {
PROXYINFO BINARY
| PROXYINFO UPGRADE
| PROXYINFO IDC
| PROXYCLUSTER [IDC] [like 'cluster_name']
| PROXYCONFIG [diff] [user] [like 'config_name']
| PROXYCONGESTION [all] [cluster_name]
| PROXYMEMORY [objpool] [num]
| PROXYNET CONNECTION [thread_id [LIMIT xx]]
| PROXYNET THREAD
| PROXYROUTE [like 'cluster [tenant [db [table]]]']
| PROXYROUTE GLOBALINDEX
| PROXYROUTE PARTITION
| PROXYROUTE QUERYASYNC
| PROXYROUTE TABLEGROUP
| PROXYROUTE TABLETLS [tablet_to_ls_num]
| PROXYROUTE RPCCTX
| PROXYRPC THREAD
| PROXYRPC REQUESTSTAT [request_type]
| PROXYSESSION
| PROXYSESSION ATTRIBUTE [id [like 'xxx']]
| PROXYSESSION STAT id [like 'xx']
| PROXYSESSION VARIABLES [all] id [like 'xx']
| PROXYSM [RPC] [sm_id]
| PROXYSTAT [refresh] [like 'name']
| WARNLOG [[[log_id], thread_id], time]
};
Parameter description
Parameter |
Description |
|---|---|
| PROXYINFO BINARY | Displays the ODP binary information in rich text format, including the version, packaging time, and MD5 value. |
| PROXYINFO UPGRADE | Displays the ODP running and upgrade information in rich text format. |
| PROXYINFO IDC | Displays the ODP IDC matching information in rich text format. |
| PROXYCLUSTER [IDC] [like 'cluster_name'] | Displays the rs_list details of the cluster. You can use the like option to perform a fuzzy match. The like option supports the % and _ wildcards. For example, you can execute the show proxycluster like "%ob%"; command. If you configure the IDC option, the idc_list details of the cluster are displayed. |
| PROXYCONFIG [diff] [user] [like 'config_name'] | Displays the ODP configuration items. If you configure the diff option, only the configuration items that are different from the default parameters are displayed. If you configure the diff user option, only the user-level configuration items that are different from the default parameters are displayed. You can use the like option to perform a fuzzy match. The like option supports the % and _ wildcards. For example, you can execute the show proxyconfig diff user like "%cpu%"; command. |
| PROXYCONGESTION [all] [cluster_name] | Displays the information of all clusters of ODP. The following table describes the different scenarios based on the configured parameters.
NoteWhen ODP is of V1.1.2 or earlier, you do not need to enclose the |
| PROXYMEMORY [objpool] [num] | Displays the memory usage of ODP, including the memory allocated to each module, the memory currently in use, and the module type. This information helps analyze the performance of ODP. After you specify a number (num) in the command, the memory allocation stack is displayed. The maximum number of layers that can be printed is 10. To use this feature, you must modify the mem_leak_check_mod_name and mem_leak_check_class_name parameters. |
| PROXYNET CONNECTION [thread_id [LIMIT xx]] | Displays the internal attribute status of all network connections on ODP. You can specify the thread_id parameter to display the connection status of a specified thread. If you do not specify the thread_id parameter, the attribute status of all connections on ODP is displayed by default. If you specify the thread id parameter, you can use the LIMIT [offset,] rows and LIMIT rows OFFSET offset options. The syntax of these options is fully compatible with that of MySQL. When you set the rows parameter to -1, all rows are displayed.
NoteFor more information, see Network connections. |
| PROXYNET THREAD | Displays the internal attribute status of each working thread of ODP. The number of working threads of ODP is controlled by the work_thread_num parameter. |
| PROXYROUTE [like 'cluster [tenant [db [table]]]'] | Displays the internal table entry status of ODP. By default, the status of all table entries is displayed. You can use the like option to perform a fuzzy match. The like option supports the % and _ wildcards. For example, you can execute the show proxyroute like 'obcluster sy_ oceanba% ob_all_%'; command. The SQL routing address information of ODP is stored in table entries. Each table entry is identified by the cluster name, tenant name, database name, and table name. If an SQL statement does not specify a table name, the __all_dummy table is used to mark the internal table entry. |
| PROXYROUTE GLOBALINDEX | Displays the OBKV global index information of ODP. You can modify the partition_location_expire_relative_time parameter to control the existence time of the cached information. |
| PROXYROUTE PARTITION | Displays the partition information of ODP. You can modify the partition_location_expire_relative_time parameter to control the existence time of the cached information. |
| PROXYROUTE QUERYASYNC | Displays the OBKV asynchronous query information of ODP. You can modify the partition_location_expire_relative_time parameter to control the existence time of the cached information. |
| PROXYROUTE TABLEGROUP | Displays the multi-column family request information of ODP. You can modify the partition_location_expire_relative_time parameter to control the existence time of the cached information. |
| PROXYROUTE TABLETLS [tablet_to_ls_num] | Displays the ls_id information in ODP. Currently, it only supports LSOp requests. tablet_to_ls_num specifies the number of data to be displayed. The cache information expiration time can be controlled by modifying the partition_location_expire_relative_time parameter. |
| PROXYROUTE RPCCTX | Displays the user information who logs in to ODP through the RPC port. You can use this command to verify whether ODP supports distributed capabilities for the logged-in user. This command cannot be cleared by using a configuration parameter. We recommend that you do not clear the login information displayed by this command, otherwise, the user may be unable to log in. |
| PROXYRPC THREAD | Displays the current request processing status of threads in ODP. |
| PROXYRPC REQUESTSTAT [request_type] | Displays the current request processing status of different threads in ODP. By default, all request statuses are displayed. You can specify the request_type parameter to display the status of a specific type of request. Currently, the request_type parameter can be set to OB_TABLE_API_LOGIN, OB_TABLE_API_EXECUTE, OB_TABLE_API_BATCH_EXECUTE, OB_TABLE_API_EXECUTE_QUERY, OB_TABLE_API_QUERY_AND_MUTATE, OB_TABLE_API_EXECUTE_QUERY_SYNC, OB_TABLE_API_DIRECT_LOAD, or OB_TABLE_API_LS_EXECUTE. If the request_type parameter is set to other values, all request types are displayed by default.
NoteThis command is used for troubleshooting. If no corresponding requests exist in ODP when the command is executed, the output result is |
| PROXYSESSION | Displays the internal status of all Client Sessions connected to the current ODP tenant. Unlike the SHOW PROCESSLIST command, the SHOW PROXYSESSION command also displays the cluster where each tenant is located. |
| PROXYSESSION ATTRIBUTE [id [like 'xxx']] | Displays the detailed internal status of the specified Client Session, including the related Server Sessions involved in the Client Session. For more information, see Client connection.
|
| PROXYSESSION STAT id [like 'xx'] | Displays the internal statistics of the specified Client Session in ODP, including the number of SQL request responses and the size of SQL request responses. For more information, see Client connection.
|
| PROXYSESSION VARIABLES [all] id [like 'xx'] | Displays the session variables of the specified Client Session. For more information, see Client connection.
|
| PROXYSM [sm_id] | Displays the internal status of each StateMachine in ODP in rich text format. You can specify the sm_id parameter to display the internal status of a specific StateMachine. |
| PROXYSM RPC [sm_id] | Displays the status of ObRpcRequestSM objects that have not been released in ODP. You can specify the sm_id parameter to query the status of a specified ObRpcRequestSM object. ObRpcRequestSM objects are released after they are executed.
NoteYou must set the rpc_enable_requestsm_info parameter to |
| PROXYSTAT [refresh] [like 'xx'] | Displays statistics in ODP.
|
| WARNLOG [[[log_id], thread_id], time] | Displays WARN and ERROR level alert logs that have a log ID greater than or equal to the specified log ID and a timestamp greater than or equal to the specified time. You can specify the thread_id parameter to query alert logs of a specified thread. If you do not care about the log ID or thread ID, you can set log_id or thread_id to -1. In this case, all alert logs with any log ID or thread ID are displayed. |
Example
View the status of ODP
View the ODP version.
show proxyinfo binary\GThe output is as follows:
*************************** 1. row *************************** name: binary info info: ObProxy-OceanBase 4.0.0-20221103165243.el7 version:RELEASE_7U MD5: REVISION:20221103165243-7c7e5821009b2d3924d1bc7a8165edf7384f6ed3 BUILD_TIME:Nov 3 2022 16:57:16View the ODP running/upgrade information.
show proxyinfo upgrade\GThe output is as follows:
*************************** 1. row *************************** name: hot upgrade info info: {is_inited:true, proxy_port:13205, proxy_ip:"10.10.10.1", is_self_md5_available:false, proxy_self_md5:"", upgrade_failures:0, check_available_failures:0, is_timeout_rollback:false, timeout_rollback_timeout_at:0, wait_cr_finish_timeout_at:0, is_self_binary:false, last_new_binary_name:"", last_new_binary_md5:"", cmd:"", hu_cont:NULL, mysql_proxy:{this:0x1107a750, is_inited:true, stop:false, is_raw_execute:false, timeout_ms:5000, client_pool:{this:0x7fd04d55d280, is_inited:true, stop:false, mc_count:1, cluster_resource:0x7fd04d5a5f80}, raw_mysql_client:{is_inited:true, info:{has_passwd_scrambled:false, user_name:"admin", database_name:"oceanbase", request_sql:""}, svr_addr_[0]="0.0.0.0", svr_addr_[1]="0.0.0.0", svr_addr_[2]="0.0.0.0"}}, info:{is_inherited:false, upgrade_version:0, need_conn_accept:true, user_rejected:0, fd:23, sub_pid:-1, graceful_exit_end_time:0, graceful_exit_start_time:0, active_client_vc_count:-1, local_addr:"10.10.10.1:13205", rc_status:"", hu_cmd:"", state:"HU_STATE_WAIT_HU_CMD", hu_status:"", is_parent:true, sub_status:"", last_parent_status:"", last_sub_status:"", upgrade_version_buf:"", argc:1, argv[0]="./bin/obproxy", inherited_argv[0]="./bin/obproxy", inherited_argv[1]="(null)", inherited_argv[2]="(null)", inherited_argv[3]="(null)"}}View the IDC matching information of ODP.
show proxyinfo idc;The output is as follows:
+-----------------+--------------+----------------+--------------+--------------+-------------+--------------+ | global_idc_name | cluster_name | match_type | regions_name | same_idc | same_region | other_region | +-----------------+--------------+----------------+--------------+--------------+-------------+--------------+ | idc1 | MetaDataBase | MATCHED_BY_IDC | ["HZ"] | ["z1", "z2"] | [] | ["z3", "z4"] | +-----------------+--------------+----------------+--------------+--------------+-------------+--------------+
View ODP connections
This section provides an example of how to view ODP connections. For more information, see Client connections.
Query the information about the client connection with the cs_id value of 2 and whose attribute name contains id.
show proxysession attribute 2 like '%id%';
The output is as follows:
+------------------------+--------------------+----------------+
| attribute_name | value | info |
+------------------------+--------------------+----------------+
| proxy_sessid | 756006681247547396 | cs common |
| cs_id | 2 | cs common |
| tid | 2230520 | cs common |
| pid | 2230520 | cs common |
| last_insert_id_version | 0 | cs var version |
| server_sessid | 2147549201 | last used ss |
| ss_id | 4 | last used ss |
| last_insert_id_version | 0 | last used ss |
+------------------------+--------------------+----------------+
View the memory usage of ODP
show proxymemory;
The output is as follows:
+-------------------------------+----------+--------------+--------------+---------+------------+-----------------------------------------------------------------------+
| mod_name | mod_type | hold | used | count | avg_used | hold bytes, alloc times and backtraces(addr2line -Cfe obproxy 0xXXXX) |
+-------------------------------+----------+--------------+--------------+---------+------------+-----------------------------------------------------------------------+
| OB_MOD_DO_NOT_USE_ME | user | 7,792 | 5,586 | 58 | 96 | |
| OB_LIGHTY_QUEUE | user | 662,848 | 657,568 | 5 | 131,513 | |
| OB_BUFFER | user | 424 | 392 | 1 | 392 | |
| OB_HASH_BUCKET | user | 24,896 | 24,672 | 7 | 3,524 | |
| OB_HASH_NODE | user | 24,160 | 24,064 | 3 | 8,021 | |
| OB_PAGE_ARENA | user | 49,152 | 48,960 | 6 | 8,160 | |
| OB_MODULE_PAGE_ALLOCATOR | user | 363,968 | 360,448 | 44 | 8,192 | |
| VECTOR | user | 40,960 | 40,800 | 5 | 8,160 | |
| OB_HASH_BUCKET_CONF_CONTAINER | user | 74,448 | 74,160 | 3 | 24,720 | |
| OB_HASH_NODE_CONF_CONTAINER | user | 71,352 | 71,064 | 9 | 7,896 | |
| OB_CONCURRENCY_OBJ_POOL | user | 36,057,568 | 35,048,480 | 197 | 177,911 | |
| OB_PROXY_DEFAULT_SYS_VARIABLE | user | 16,544 | 16,384 | 1 | 16,384 | |
| OB_PROXY_SQL_PARSE | user | 8,272 | 8,192 | 1 | 8,192 | |
| OB_PROXY_TABLE_ENTRY_MAP | user | 132,352 | 131,072 | 8 | 16,384 | |
| OB_PROXY_SQL_TABLE_ENTRY_MAP | user | 132,352 | 131,072 | 8 | 16,384 | |
| OB_PROXY_PARTITION_ENTRY_MAP | user | 529,408 | 524,288 | 8 | 65,536 | |
| OB_PROXY_INDEX_ENTRY_MAP | user | 132,352 | 131,072 | 8 | 16,384 | |
| OB_PROXY_TABLEGROUP_ENTRY_MAP | user | 33,024 | 32,768 | 8 | 4,096 | |
| OB_PROXY_TABLET_LS_ENTRY_MAP | user | 33,024 | 32,768 | 8 | 4,096 | |
| OB_PROXY_RPC_TABLE_QUERY_MAP | user | 132,352 | 131,072 | 8 | 16,384 | |
| OB_PROXY_RPC_REQ_CTX_MAP | user | 132,352 | 131,072 | 8 | 16,384 | |
| OB_PROXY_ROUTINE_ENTRY_MAP | user | 529,408 | 524,288 | 8 | 65,536 | |
| OB_PROXY_CONGESTION_ENTRY_MAP | user | 132,352 | 131,072 | 8 | 16,384 | |
| OB_PROXY_WARN_LOG_BUF | user | 19,960,336 | 19,922,944 | 19 | 1,048,576 | |
| OB_PROXY_SSL_RELATED | user | 11,640 | 11,544 | 3 | 3,848 | |
| OB_PROXY_MEM_LEAK_CHECK | user | 702,544 | 697,376 | 37 | 18,848 | |
| OB_PROXY_CLIENT_SESSION_ID | user | 20,992 | 20,704 | 9 | 2,300 | |
| OB_PROXY_DECIMAL_INT_CONST | user | 16,544 | 16,384 | 2 | 8,192 | |
| OB_ASYNC_LOG_BUFFER | user | 64,308,648 | 62,915,840 | 41,093 | 1,531 | |
| GLIBC | user | 14,835,712 | 14,655,232 | 6 | 2,442,538 | |
| OB_SQL_AUDIT | user | 0 | 0 | 0 | 0 | |
| OB_SQL_AUDIT_LAST | user | 0 | 0 | 0 | 0 | |
| TOTAL | user | 180,355,072 | 136,513,146 | 0 | 0 | |
+-------------------------------+----------+--------------+--------------+---------+------------+-----------------------------------------------------------------------+
View cluster information
Run the following command to view the OBServer node information of the specified cluster:
show proxycongestion all "obcluster";
In the preceding example, the cluster name is obcluster. You must replace it with the actual cluster name. The output is as follows:
+-----------------+-----------+------------+--------------------+--------------+-----------------+----------------------+----------------+---------------------+---------------------+--------------------+---------------------+---------------------+----------------------+----------------------+-----------+
| cluster_name | zone_name | zone_state | server_ip | server_state | alive_congested | last_alive_congested | dead_congested | last_dead_congested | stat_alive_failures | stat_conn_failures | conn_last_fail_time | conn_failure_events | alive_last_fail_time | alive_failure_events | ref_count |
+-----------------+-----------+------------+--------------------+--------------+-----------------+----------------------+----------------+---------------------+---------------------+--------------------+---------------------+---------------------+----------------------+----------------------+-----------+
| obcluster | zone1 | ACTIVE | 10.10.10.1:13201 | ACTIVE | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 |
+-----------------+-----------+------------+--------------------+--------------+-----------------+----------------------+----------------+---------------------+---------------------+--------------------+---------------------+---------------------+----------------------+----------------------+-----------+
View internal statistics of ODP
Run the following command to view the statistics whose names contain global in ODP:
show proxystat refresh like '%global%';
The output is as follows. global_client_connections_currently_open indicates the number of client connections to ODP. global_connections_currently_open indicates the sum of the number of client connections to ODP and the number of ODP connections to OceanBase Database.
+---------------------------------------------+-------+--------------+
| stat_name | value | persist_type |
+---------------------------------------------+-------+--------------+
| get_congestion_from_global_cache_miss | 0 | PERSISTENT |
| get_congestion_from_global_cache_hit | 0 | PERSISTENT |
| kick_out_routine_entry_from_global_cache | 0 | PERSISTENT |
| gc_routine_entry_from_global_cache | 0 | PERSISTENT |
| get_routine_entry_from_global_cache_dirty | 0 | PERSISTENT |
| get_routine_entry_from_global_cache_hit | 0 | PERSISTENT |
| kick_out_partition_entry_from_global_cache | 0 | PERSISTENT |
| gc_partition_entry_from_global_cache | 0 | PERSISTENT |
| get_partition_entry_from_global_cache_dirty | 0 | PERSISTENT |
| get_partition_entry_from_global_cache_hit | 0 | PERSISTENT |
| kick_out_table_entry_from_global_cache | 0 | NULL |
| gc_table_entry_from_global_cache | 0 | NULL |
| get_pl_from_global_cache_dirty_stat | 0 | PERSISTENT |
| get_pl_from_global_cache_hit | 2 | PERSISTENT |
| global_accepts_currently_open | 4 | NULL |
| global_connections_currently_open | 1 | NULL |
| global_client_connections_currently_open | 1 | NULL |
+---------------------------------------------+-------+--------------+
Query an alert log
Query alert logs whose time is not earlier than 2016-09-13 11:20:52.251.
show warnlog -1, -1, "2016-09-13 11:20:52.251";Setting
log_idandthread_idto-1indicates that all alert logs not earlier than the specified time are queried.Query alert logs whose log ID is not earlier than 1000, thread ID is 36592, and time is not earlier than 2016-09-13 11:20:52.251.
show warnlog 1000, 36592, "2016-09-13 11:20:52.251";
View routing information
View partition information
show proxyroute partition;The output is as follows:
+----------+--------------+-------+-----------------+------------------+---------------------+---------------------+---------------------+---------------------+---------------------+----------------------+----------------------------------------------------------------------------------+ | table_id | partition_id | state | cluster_version | schema_version | create_time | last_valid_time | last_access_time | last_update_time | expire_time | relative_expire_time | server addr | +----------+--------------+-------+-----------------+------------------+---------------------+---------------------+---------------------+---------------------+---------------------+----------------------+----------------------------------------------------------------------------------+ | 500005 | 200010 | AVAIL | 4 | 1747194026487400 | 2025-05-14 11:42:21 | 2025-05-14 11:42:21 | 2025-05-14 11:42:21 | 1970-01-01 08:00:00 | 1970-01-01 08:00:00 | 1970-01-01 08:00:00 | server[0]=127.0.0.1:31604,leader,FULL; server[1]=127.0.0.1:31606,follower,FULL; | | 500005 | 200003 | AVAIL | 4 | 1747194026487400 | 2025-05-14 11:42:03 | 2025-05-14 11:42:03 | 2025-05-14 11:42:03 | 1970-01-01 08:00:00 | 1970-01-01 08:00:00 | 1970-01-01 08:00:00 | server[0]=127.0.0.1:31604,leader,FULL; server[1]=127.0.0.1:31606,follower,FULL; | | 500005 | 200024 | AVAIL | 4 | 1747194026487400 | 2025-05-14 11:42:02 | 2025-05-14 11:42:02 | 2025-05-14 11:42:02 | 1970-01-01 08:00:00 | 1970-01-01 08:00:00 | 1970-01-01 08:00:00 | server[0]=127.0.0.1:31604,leader,FULL; server[1]=127.0.0.1:31606,follower,FULL; | +----------+--------------+-------+-----------------+------------------+---------------------+---------------------+---------------------+---------------------+---------------------+----------------------+----------------------------------------------------------------------------------+View global index information
show proxyroute globalindex;The output is as follows:
+----------+---------------+------------------+-------+-----------------+------------------+---------------------+---------------------+---------------------+---------------------+---------------------+----------------------+ | table_id | data_table_id | index_table_name | state | cluster_version | schema_version | create_time | last_valid_time | last_access_time | last_update_time | expire_time | relative_expire_time | +----------+---------------+------------------+-------+-----------------+------------------+---------------------+---------------------+---------------------+---------------------+---------------------+----------------------+ | 500391 | 500390 | __idx_500390_idx | AVAIL | 2 | 1699412694079328 | 2025-05-15 20:14:47 | 2025-05-15 20:14:47 | 2025-05-15 20:14:47 | 1970-01-01 08:00:00 | 1970-01-01 08:00:00 | 1970-01-01 08:00:00 | +----------+---------------+------------------+-------+-----------------+------------------+---------------------+---------------------+---------------------+---------------------+---------------------+----------------------+View asynchronous query information
show proxyroute queryasync;The output is as follows:
+-------------------------+-------------------------+------------------+----------+---------------+--------------------+-------------+-------------------------------+---------+ | client_query_session_id | server_query_session_id | current_position | table_id | data_table_id | global_index_query | first_query | server_info | state | +-------------------------+-------------------------+------------------+----------+---------------+--------------------+-------------+-------------------------------+---------+ | 7 | 0 | 5 | 501187 | 501187 | N | Y | server:*Not IP address [0]*:0 | AVAIL | | 11 | 0 | 12 | 501230 | 501230 | N | N | server:127.0.0.1:31605 | DELETED | | 12 | 0 | 0 | 501230 | 501230 | N | N | server:127.0.0.1:31605 | DELETED | +-------------------------+-------------------------+------------------+----------+---------------+--------------------+-------------+-------------------------------+---------+View the ls_id information.
View the ls_id information in ODP and configure the output to show only two tablet->ls mappings.
show proxyroute tabletls 2;The following information is returned. The value after
->in themap[0]=200022->1001field of thetablet_to_ls_mapcolumn is thels_id. The value1001in the sample shows that the LSOp request calculation is accurate.+-----------+----------+-------+-----------------+----------------+---------------------+---------------------+---------------------+---------------------+---------------------+----------------------+--------------------------------------------+ | tenant_id | table_id | state | cluster_version | schema_version | create_time | last_valid_time | last_access_time | last_update_time | expire_time | relative_expire_time | tablet_to_ls_map | +-----------+----------+-------+-----------------+----------------+---------------------+---------------------+---------------------+---------------------+---------------------+----------------------+--------------------------------------------+ | 1004 | 500005 | AVAIL | 4 | 0 | 2025-05-14 11:42:21 | 2025-05-14 11:42:21 | 2025-05-14 11:42:21 | 1970-01-01 08:00:00 | 1970-01-01 08:00:00 | 1970-01-01 08:00:00 | map[0]=200022->1001; map[1]=200023->1001; | +-----------+----------+-------+-----------------+----------------+---------------------+---------------------+---------------------+---------------------+---------------------+----------------------+--------------------------------------------+View the OBKV login information saved in ODP.
show proxyroute rpcctx;The following information is returned. If the value of the
is_support_distributationcolumn isN, the tenant does not support the distributed capability, as in this sample.+-----------------------------------+-------------+-----------+---------------+----------------------------------------------+---------------------------+ | cluster_name | tenant_name | user_name | database_name | full_name | is_support_distributation | +-----------------------------------+-------------+-----------+---------------+----------------------------------------------+---------------------------+ | ob2.chengzhilei.czl.11.158.77.130 | mysql | root | test | root@mysql#ob2.chengzhilei.czl.11.158.77.130 | N | +-----------------------------------+-------------+-----------+---------------+----------------------------------------------+---------------------------+
View information about the request
View the status of ObRpcRequestSMs that have not been released in ODP.
ObRpcRequestSM is released after the request is executed. This example simulates a scenario where a subrequest is not released and specifies the sm_id to view the status of a single ObRpcRequestSM.
obclient> show proxysm rpc 28\GThe output is as follows:
*************************** 1. row *************************** sm_id: 28 trace_id: Y1F0CC1EF9F20D-0000000000000002-0-0 client_state: RPC_REQ_CLIENT_DONE server_state: RPC_REQ_SERVER_SHARDING_REQUEST_HANDLING sm_state: RPC_REQ_SM_REQUEST_CLEANUP cs_id: 134217732 sm_info: HISTORY: [0]=={fileline:obproxy/proxy/rpc/ob_rpc_request_sm.cpp:1197; event:4294967295; reentrancy:1;} [1]=={fileline:obproxy/proxy/rpc/ob_rpc_request_sm.cpp:1382; event:4294967295; reentrancy:2;} [2]=={fileline:obproxy/proxy/rpc/ob_rpc_request_sm.cpp:2409; event:4294967295; reentrancy:1;} [3]=={fileline:obproxy/proxy/rpc/ob_rpc_request_sm.cpp:2743; event:1101; reentrancy:1;} [4]=={fileline:obproxy/proxy/rpc/ob_rpc_request_sm.cpp:3150; event:4294967295; reentrancy:1;} [5]=={fileline:obproxy/proxy/rpc/ob_rpc_request_sm.cpp:4837; event:4294967295; reentrancy:1;} [6]=={fileline:obproxy/proxy/rpc/ob_rpc_request_sm.cpp:4852; event:102; reentrancy:1;}View the requests being processed by the current thread.
show proxyrpc thread;The output is as follows. The
ThreadTypefield indicates the thread type. The output value can be0,1,2, or3:0indicates a regular working thread.1and2indicate internal threads.3indicates an OBKV working thread.
+----------+------------+------------------------+---------------------------+--------------+--------------+-------------+ | ThreadID | ThreadType | ClientHandlingReqCount | ThreadHandlingSubReqCount | ClientReqQps | SingleReqQps | ShardReqQps | +----------+------------+------------------------+---------------------------+--------------+--------------+-------------+ | 2 | 0 | 72 | 498364 | 0 | 207 | 997 | | 3 | 0 | 75 | 575110 | 0 | 206 | 1199 | | 4 | 0 | 72 | 535484 | 0 | 208 | 1105 | | 5 | 0 | 72 | 526828 | 0 | 209 | 972 | | 6 | 0 | 57 | 594106 | 0 | 206 | 1073 | | 7 | 0 | 72 | 554829 | 0 | 209 | 839 | | 0 | 0 | 62 | 548355 | 0 | 204 | 1043 | | 1 | 0 | 78 | 521760 | 0 | 205 | 975 | | 259 | 3 | 0 | 0 | 0 | 1903 | 0 | | 260 | 3 | 0 | 0 | 0 | 1914 | 0 | | 261 | 3 | 0 | 0 | 0 | 1915 | 0 | | 262 | 3 | 0 | 0 | 0 | 1903 | 0 | | 263 | 3 | 0 | 0 | 0 | 1899 | 0 | | 264 | 3 | 0 | 0 | 0 | 1909 | 0 | | 265 | 3 | 0 | 0 | 0 | 1924 | 0 | | 266 | 3 | 0 | 0 | 0 | 1913 | 0 | +----------+------------+------------------------+---------------------------+--------------+--------------+-------------+View the status of requests being processed by different threads.
Run this command when troubleshooting. If no corresponding request exists in ODP, the output is
0for all fields. The following example shows the status of all request types. You can also specify a request type to query, such asOB_TABLE_API_LS_EXECUTE. For example, run theshow proxyrpc requeststat OB_TABLE_API_LS_EXECUTE;command to query the status ofOB_TABLE_API_LS_EXECUTErequests.show proxyrpc requeststat;The output is as follows. The
ThreadTypefield indicates the thread type, which can be0,1,2, or3.0indicates a normal worker thread.1and2indicate internal threads.3indicates an OBKV worker thread.
+----------+------------+---------------------+-------------------+---------------------+---------------------+--------------+-----------------+-------------------+----------------------+-------------------+ | ThreadID | ThreadType | AnalyzeRequestCount | BuildClusterCount | GetGlobalindexCount | GetPartitionIDCount | GetLSIDCount | InShardingCount | SendToServerCount | AnalyzeResponseCount | SendToClientCount | +----------+------------+---------------------+-------------------+---------------------+---------------------+--------------+-----------------+-------------------+----------------------+-------------------+ | 2 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 103 | 0 | 16 | | 3 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 82 | 0 | 39 | | 4 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 80 | 0 | 29 | | 5 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 61 | 0 | 46 | | 6 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 89 | 0 | 19 | | 7 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 78 | 0 | 27 | | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 83 | 0 | 19 | | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 81 | 0 | 44 | | 259 | 3 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | 260 | 3 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | 261 | 3 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | 262 | 3 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | 263 | 3 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | 264 | 3 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | 265 | 3 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | 266 | 3 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +----------+------------+---------------------+-------------------+---------------------+---------------------+--------------+-----------------+-------------------+----------------------+-------------------+