ob_org_cluster_id is used to set the CLUSTER_ID at the OceanBase session level. This value is persisted in transaction logs.
Typically, you do not need to set the ob_org_cluster_id variable, as OceanBase Database uses a default value when generating logs (Clogs). OMS can implement data filtering functionality through ob_org_cluster_id. For detailed information and configuration on the OMS data filtering feature, see Create a data migration project for migrating from MySQL to a MySQL-compatible tenant of OceanBase Database in OceanBase Migration Service.
For example, if you set the cluster_id blacklist for the OMS OBCDC component to cluster_id_black_list=2147473648 and set the session variable ob_org_cluster_id to 2147473648; when writing data to an OBServer node. After receiving the data, OBCDC filters out data with a cluster_id equal to 2147473648.
Attribute |
Description |
|---|---|
| Parameter type | int |
| Default Value | 0 |
| Value range | [0, 4294967295] |
| Effective Scope | SESSION |
| Whether to participate in serialization | Yes |