Overview
In a MySQL-compatible tenant, the GV$OB_KV_CLIENT_INFO view provides access to the configuration parameter information of the client connections in the current OBKV-compatible tenant.
Columns
Field |
Type |
Nullable |
Description |
|---|---|---|---|
| client_id | bigint | NO | Client ID |
| client_ip | varchar:MAX_IP_ADDR_LENGTH | NO | Client IP Address |
| client_port | bigint | NO | Client Port |
| svr_ip | varchar:MAX_IP_ADDR_LENGTH | NO | IP Address of the Server |
| svr_port | bigint | NO | Server Port |
| tenant_id | bigint | NO | Tenant ID |
| user_name | varchar::OB_MAX_USER_NAME_LENGTH | NO | Username |
| first_login_ts | timestamp(6) | NO | First Login Time |
| last_login_ts | timestamp(6) | NO | Last Login Time |
| client_info | varchar:2048 | NO | Client Information JSON String |
The client_info field is a JSON string in the following format:
{
"client_id": 242153145,
"runtime": {
"rpc.execute.timeout": "3000",
"rpc.operation.timeout": "10000",
"runtime.max.wait": "3000",
"runtime.retry.interval": "1",
"runtime.retry.times": "1",
"connection.max.expired.time": "8"
},
"log": {
"slow.query.monitor.threshold": "10"
},
"route": {
"metadata.refresh.interval": "60000",
"continuous.failure.ceiling": "100",
"server.address.caching.timeout": "3600000",
"server.address.priority.timeout": "1800000",
"table.entry.acquire.connect.timeout": "500",
"table.entry.acquire.socket.timeout": "3000",
"table.entry.refresh.interval.base": "100",
"table.entry.refresh.interval.ceiling": "1600",
"table.entry.refresh.try.times": "3"
},
"thread_pool": {
"runtime.batch.executor": "false"
}
}
The parameters in the JSON fields are described as follows:
Parameter |
Default value |
Description |
|---|---|---|
| metadata.refresh.interval | 60000 | The time interval for refreshing metadata. |
| rpc.execute.timeout | 3000 | The timeout period for the socket that executes the RPC request. |
| rpc.operation.timeout | 10000 | The timeout period for an internal RPC request in OceanBase AI Database. |
| runtime.continuous.failure.ceiling | 100 | Maximum consecutive running failures. When this limit is reached, the table address will be refreshed. |
| runtime.max.wait | 3000 | A single execution timeout will be retried within the timeout period. |
| runtime.retry.interval | 1 | The time interval for retrying when an error occurs during execution. |
| runtime.retry.times | 1 | The number of retries when a retryable error occurs during execution. |
| server.address.caching.timeout | 3600000L | The expiration time of the server address cache. |
| server.address.priority.timeout | 1800000L | The expiration time of the server address priority. |
| slow.query.monitor.threshold | 10 | The runtime threshold for a slow operation to be recorded in the MONITOR log. |
| table.entry.acquire.connect.timeout | 500 | The timeout period for refreshing the TABLE address request to create a connection. |
| table.entry.acquire.socket.timeout | 3000 | The socket timeout period for refreshing the TABLE address. |
| table.entry.refresh.interval.base | 100 | The basic time interval for refreshing the TABLE address. |
| table.entry.refresh.interval.ceiling | 1600 | Maximum time interval for refreshing the TABLE address. |
| table.entry.refresh.try.times | 3 | The number of attempts to refresh the TABLE address. |
| runtime.batch.executor | false | Thread Pool for Concurrent Execution in Batch Requests |
| connection.max.expired.time | 8 | The maximum time interval for refreshing and logging in again when a client connection expires. |