This topic describes the recommended configuration parameters and version requirements for the automatic partition feature of OceanBase Database, including configuration suggestions for OceanBase Database, OceanBase Database Proxy (ODP), and KV clients.
OceanBase Database configuration
Version recommendations
It is recommended to use OceanBase Database V4.4.0 or later.
Split-related parameters
Parameter name |
Recommended value |
Description |
|---|---|---|
| enable_auto_split | True | Enables the automatic partition splitting feature. |
| auto_split_tablet_size | 16 GB | Sets the threshold for triggering automatic partitioning to avoid the number of table-level partitions exceeding the allowed upper limit. |
Load balancing parameters
After automatic partitioning, it is recommended to adjust the following parameters to accelerate load balancing (partition balancing) of the OceanBase cluster:
Parameter name |
Recommended value |
Description |
|---|---|---|
| partition_balance_schedule_interval | 600s | Shortens the partition balancing scheduling interval to improve resource utilization of new partitions, that is, to schedule partition balancing more quickly. |
ODP configuration
ODP version recommendations
It is recommended to use ODP V4.3.1.4-62025012317.
ODP parameter recommendations
To avoid performance jitter caused by delayed Proxy route refresh due to automatic split changes, it is recommended to adjust the following parameters.
Parameter name |
Recommended value |
Description |
|---|---|---|
| is_need_skip_delay_interval_schema_changed | True | When the partition schema_version is less than the table's schema_version, the partition route is refreshed directly without being affected by the interval time. |
KV client configuration
KV version recommendations
- If you use OBKV, it is recommended to use V1.4.0 or later.
- If you use OBHBase V1.x, it is recommended to use V1.1.0 or later.
- If you use OBHBase V2.x, it is recommended to use V2.1.0 or later.
KV parameter recommendations
It is recommended to adjust the following parameters to avoid performance jitter or errors caused by automatic 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 retryable errors. |
| runtime.max.wait | 3000ms | The retry timeout. An error is reported when either this or the retry count is satisfied. |
| runtime.retry.interval | 1ms | The retry wait interval. |