This topic describes the recommended configuration parameters and version requirements for the automatic partitioning feature of OceanBase AI Database, including suggestions for configuring OceanBase AI Database, OceanBase Database Proxy (ODP), and the Key-Value client.
Configuration for OceanBase AI Database
Parameters related to partition splitting
Parameter name |
Recommended value |
Description |
|---|---|---|
| enable_auto_split | True | Enable automatic partition splitting. |
| auto_split_tablet_size | 16GB | Set the threshold for triggering automatic partitioning to prevent the number of table-level partitions from exceeding the allowed limit. |
Load balancing parameters
After enabling automatic partitioning, we recommend that you adjust the following parameters to accelerate load balancing (partition balancing) in the OceanBase AI Database cluster:
Parameter name |
Recommended value |
Description |
|---|---|---|
| partition_balance_schedule_interval | 600s | Shorten the partition balancing scheduling interval to improve resource utilization of new partitions, enabling faster partition balancing scheduling. |
ODP configuration
Recommended ODP version
We recommend that you use ODP V4.3.1.4-62025012317.
Recommended ODP parameters
To avoid performance jitter caused by delayed Proxy route refresh due to automatic partition splitting changes, we recommend that you adjust the following parameters.
Parameter name |
Recommended value |
Description |
|---|---|---|
| is_need_skip_delay_interval_schema_changed | True | When the partition's schema_version is earlier than the table's schema_version, the partition routing is refreshed directly without being affected by the interval. |
Key-Value client configuration
Recommended Key-Value versions
- If you use OBKV, we recommend that you use V1.4.0 or later.
- If you use OBHBase V1.x, we recommend that you use V1.1.0 or later.
- If you use OBHBase V2.x, we recommend that you use V2.1.0 or later.
Recommended Key-Value parameters
We recommend that you adjust the following parameters to avoid performance jitter or errors caused by automatic partition splitting.
Parameter name |
Recommended value |
Description |
|---|---|---|
| table.entry.refresh.interval.wait | True | Prevents multiple threads from refreshing simultaneously while waiting for the currently refreshing thread to complete, avoiding reading old routes. This is enabled by default on the client. |
| server.enable.rerouting | False | Due to client implementation reasons, this is mutually exclusive with the single-shard refresh feature. This is disabled by default on the client. |
| runtime.retry.times | 100 | The number of retries for a retriable error. |
| runtime.max.wait | 3000ms | Retry timeout period. An error is reported if either the retry timeout period or the number of retries is exceeded. |
| runtime.retry.interval | 1ms | Retry wait interval. |