Overview
replica_parallel_migration_mode specifies the mode for the log stream replica parallel migration feature.
Privilege requirements
Query parameters
The
SHOW PARAMETERSstatement or theGV$OB_PARAMETERSview can be used by thesystenant and all user tenants to query this parameter.Modify parameters
Both the
systenant and user tenants can modify this parameter.
Attributes
Attribute |
Description |
|---|---|
| Parameter type | String |
| Default Value | auto |
| Value range |
|
| Modifiable | Yes, you can use theALTER SYSTEM SETStatement modification. |
| Whether to restart the OBServer node for the change to take effect | No, the setting takes effect immediately. |
Usage instructions
When setting this parameter, note the following:
In the physical standby database scenario, the primary and standby tenants have different requirements for the parallel migration of log stream replicas:
In typical scenarios, the primary tenant may not require the parallel migration feature, as migrating multiple replicas simultaneously involves a large volume of data, which could impact the I/O performance of the leader replica.
Standby tenants have a high demand for parallel migration, which can reduce the probability of replica rebuilds on the standby tenant.
When using the parallel migration feature, minimize the impact on the business of the existing primary database (primary tenant). If you need to accelerate scaling based on your business requirements, you can enable the parallel migration feature.
In a physical standby scenario, this parameter must be set for both the primary and standby tenants.
Configuration example
The user tenant enables the parallel migration feature for itself.
obclient> ALTER SYSTEM SET replica_parallel_migration_mode = 'on';