This topic describes the recommended configuration parameters and version requirements for the automatic partitioning feature of OceanBase Database. It also provides configuration recommendations for OceanBase Database, OceanBase Database Proxy (ODP), and KV clients.
OceanBase Database configuration
Version recommendation
We recommend that you use OceanBase Database V4.4.0 or later.
Splitting-related parameters
| Parameter | Recommended value | Description |
|---|---|---|
| enable_auto_split | True | Enables the automatic partition splitting feature. |
| auto_split_tablet_size | 16GB | Sets the threshold for triggering automatic partition splitting to prevent the number of partitions from exceeding the allowed limit. |
Load balancing parameters
After automatic partition splitting, we recommend that you adjust the following parameters to accelerate the load balancing (partition balancing) of the OceanBase cluster:
| Parameter | Recommended value | Description |
|---|---|---|
| partition_balance_schedule_interval | 600s | Shortens the partition balancing scheduling interval to improve the resource utilization of new partitions, allowing for faster partition balancing. |
ODP configuration
ODP version recommendation
We recommend that you use ODP V4.3.1.4-62025012317.
ODP parameters
To avoid performance fluctuations caused by the proxy not refreshing the routing in a timely manner due to changes in automatic splitting, we recommend that you adjust the following parameters.
| Parameter | Recommended value | Description |
|---|---|---|
| is_need_skip_delay_interval_schema_changed | True | When the partition schema_version is less than the table schema_version, the partition route is refreshed directly without being affected by the interval. |
KV client configuration
Recommended KV 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 KV parameters
We recommend that you adjust the following parameters to avoid performance jitter or errors caused by automatic splitting.
| Parameter | Recommended value | Description |
|---|---|---|
| table.entry.refresh.interval.wait | True | Avoids multiple threads from refreshing simultaneously and waits for the current refresh thread to complete, preventing the client from reading outdated routing information. This parameter is enabled by default. |
| server.enable.rerouting | False | This parameter is disabled by default for client-side implementation reasons and is mutually exclusive with the single-shard refresh feature. |
| runtime.retry.times | 100 | The number of retries for retryable errors. |
| runtime.max.wait | 3000ms | The retry timeout period. An error is returned if either the retry count or the timeout period is reached. |
| runtime.retry.interval | 1ms | The interval between retries. |