After you purchase the Binlog service, you can view the basic information, resource configuration, subscription connection list, and monitoring metrics of the Binlog service. You can also modify the retention duration of Binlog files, enable or disable the DDL output compatibility, and perform other operations such as changing configuration and disabling the Binlog service as needed.
Access the details page
Log in to the OceanBase Cloud console.
On the Instances page, click the name of the target instance to go to the Overview page of the instance.
In the left-side navigation pane, click Tenants. In the tenant list, click the name of the target MySQL-compatible tenant to go to the Overview page of the tenant.
In the left-side navigation pane, click Binlog to go to the details page, where you can view information about the Binlog service.
The operations that you can perform on a Binlog service depend on its status.
Status Supported operations Running Modify the configuration, view the monitoring metrics, and disable the Binlog service Changing Config View the monitoring metrics Service Error View the monitoring metrics and disable the Binlog service Stopped View the monitoring metrics and disable the Binlog service Change configuration
You can click Change Config in the upper-right corner to change the Binlog configuration. For more information, see Change configuration.
View the monitoring metrics
You can click View Monitoring in the upper-right corner to go to the Metrics > Binlog page, where you can view the monitoring metrics of the Binlog service. For more information, see View the monitoring metrics of the Binlog service.
Disable the Binlog service
You can click ... in the upper-right corner and then click Disable Binlog Service to disable the Binlog service that is no longer maintained. For more information, see Disable the Binlog service.
Note
After you stop the Binlog service, all the generated log files will be deleted and cannot be recovered. The storage space occupied by the log files will also be released. proceed with caution.
View basic information
In the Basic Information section, you can view the following information.
| Parameter | Description |
|---|---|
| Status | The running status of the Binlog service. Valid values: Running, Changing Config, Service Error, and Stopped. |
| Enabled At | The time when the Binlog service was enabled, which is displayed in the time zone configured for OceanBase Cloud. For example, UTC+8. |
| DDL Output Compatibility | You can enable or disable the DDL output compatibility feature as needed. For more information, see the "Enable or disable DDL output compatibility" section below. |
| Retention Duration | The maximum retention duration for Binlog files in the Binlog service, which is 18 hours by default. For more information, see the "Modify the retention duration of Binlog files" section below. |
| Earliest/Current Conversion Point | Displays the earliest and current conversion points. |
Enable or disable DDL output compatibility
In the Basic Information section, click the DDL Output Compatibility switch to enable or disable DDL output compatibility.
When you purchase the Binlog service, the MySQL compatibility parameters are set. These parameters are tenant-level configurations. After you purchase the Binlog service, DDL Output Compatibility is enabled by default for each tenant in the same instance. This means that the output of commands like
SHOW CREATE TABLEandSHOW CREATE DATABASEis fully compatible with MySQL. For example, after you enable the Binlog service, it will by default set_show_ddl_in_compat_modeto 1, which makesSHOW CREATE TABLEreturn statements compatible with MySQL. If you want to display the unique statement syntax of OceanBase Database, set_show_ddl_in_compat_modeto 0 in the connection session, or disable the DDL output compatibility feature in the Binlog service.If DDL Output Compatibility is not enabled, additional parameters such as OceanBase-specific storage information will be included, which may affect the usage of tools that rely on the output of this command.
Note
Tenants in MySQL compatible mode of OceanBase Database have unique features such as subpartitions and LIST DEFAULT partitions. If you have created tables using these features, enabling the DDL output compatibility feature will result in some differences between the displayed content and the actual schema of OceanBase Database. Use this feature with caution.
After the confirmation dialog box appears, click OK or Close.
If you want to enable DDL output compatibility, click OK.
If you want to disable DDL output compatibility, click Close.
Modify the retention duration of Binlog files
In the Basic Information section, click the edit icon next to Retention Duration.
In the OK dialog box, set the new retention duration.
You can set the retention duration to 1 to 240 hours. Binlog files that exceed the retention duration will be automatically deleted. However, Binlog files are also limited by the available storage space. If the storage space reaches its maximum capacity, Binlog files that are within the retention duration may also be deleted.
After you set the retention period, click OK.
View resource configuration
In the Resource Configuration section, you can view the following information.
| Parameter | Description |
|---|---|
| Free Quota | Displays the free quota for compute units based on tenant specification. The free quota for storage space is 10 GiB. |
| Compute Unit | A Compute Unit (CU) represents the capability of the Binlog service to collect and convert Clogs and provide subscriptions. It shows the upper limits for converting PRS/BPS and the upper limits for subscriptions, as well as the maximum number of subscription connections. |
| Storage | The storage space used by the Binlog service for storing converted Binlog files.
|
View the subscription connections
A single compute unit provides one subscription connection, but the maximum number of subscription connections is 20. After reaching the limit, the number of subscription connections does not increase with the addition of more compute units. In the Subscription Connections section, you can view information such as the username, client IP address, port, sending site, sending latency (in ms), sending RPS, and current network traffic of each subscription connection.