Note
This view is introduced in V4.3.4 and applies to the OBKV-Table client.
Purpose
In the system tenant, the V$OB_KV_CLIENT_INFO view can be used to query the configuration parameters of all OBKV tenant clients connected to the current node.
Columns
| Column | 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 node |
| svr_port | bigint | NO | Port of the server node |
| 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 | JSON string of client information |
The client_info parameter 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:
| Column | Default value | Description |
|---|---|---|
| metadata.refresh.interval | 60000 | Time interval for refreshing METADATA. |
| rpc.execute.timeout | 3000 | Socket timeout for executing RPC requests. |
| rpc.operation.timeout | 10000 | Timeout for OceanBase to execute RPC requests. |
| runtime.continuous.failure.ceiling | 100 | Upper limit on the number of consecutive failures, which refreshes the address of the TABLE. |
| runtime.max.wait | 3000 | The timeout for a single execution. If the execution exceeds the timeout, the system will retry the execution. |
| runtime.retry.interval | 1 | Time interval for retrying when an error occurs. |
| runtime.retry.times | 1 | Number of retries when a retryable error occurs during execution. |
| server.address.caching.timeout | 3600000L | Expiration time for caching the server address. |
| server.address.priority.timeout | 1800000L | Expiration time for caching the priority of the server address. |
| slow.query.monitor.threshold | 10 | Threshold for the runtime of slow operations recorded in the MONITOR log. |
| table.entry.acquire.connect.timeout | 500 | Timeout for creating a connection when requesting the address of the TABLE. |
| table.entry.acquire.socket.timeout | 3000 | SOCKET timeout for requesting the address of the TABLE. |
| table.entry.refresh.interval.base | 100 | Base time interval for refreshing the address of the TABLE. |
| table.entry.refresh.interval.ceiling | 1600 | Maximum time interval for refreshing the address of the TABLE. |
| table.entry.refresh.try.times | 3 | Number of attempts for refreshing the address of the TABLE. |
| runtime.batch.executor | false | Concurrent thread pool for processing batch requests. |
| connection.max.expired.time | 8 | Maximum time interval for refreshing the client connection and relogging in. |