Update and upgrade

Upgrade the binlog service

You can run the env/deploy.sh script to upgrade obbinlog. To do so, perform the following steps:

1. Download the obbinlog RPM package of the target version and decompress it. This operation does not directly install obbinlog.

   wget https://mirrors.aliyun.com/oceanbase/community/stable/el/7/x86_64/obbinlog-ce-4.2.0-100000152024122710.el7.x86_64.rpm
   rpm2cpio obbinlog-ce-4.2.0-100000152024122710.el7.x86_64.rpm | cpio -idv
   

   The decompressed RPM package is stored in the ./home/ds/oblogproxy directory.

2. Stop the binlog server.

   Notice

   This operation stops the current node from receiving new client requests, but does not affect the running binlog instances or the clients that are consuming binlogs.

   cd /home/ds/oblogproxy
   ./run.sh stop
   

3. Use the ./home/ds/oblogproxy/env/deploy.sh script in the new package to update the original package.

   cd ./home/ds/oblogproxy/env
   sh deploy.sh -m upgrade -d /home/ds/oblogproxy
   

   In this example, the -d parameter specifies the original installation path of obbinlog. Modify it based on the actual installation path.

4. Start the binlog server.

   cd /home/ds/oblogproxy
   ./run.sh start
   

   The upgrade of a binlog server node is completed.

Rotating-upgrade binlog instances

You can upgrade binlog instances of a binlog task in rotating mode to reduce impact on your business.

If your binlog task involves multiple binlog instances, perform the following steps:

1. Run the SHOW BINLOG STATUS command to query the primary binlog instance of the current binlog task. For more information about the command, see Task management.

2. Run the SHOW BINLOG INSTANCES command to query all binlog instances of the current binlog task. For more information about the command, see Instance management.

3. Upgrade the nodes where the binlog instances other than the primary one reside. For more information, see the Upgrade the binlog service section in this topic.

4. Run the STOP BINLOG INSTANCE and START BINLOG INSTANCE commands to restart the binlog instances on the upgraded nodes. For more information about the commands, see Instance management.

5. Run the SWITCH MASTER INSTANCE command to switch an upgraded binlog instance to be the primary instance of the current tenant. For more information about the command, see Instance management.

6. Upgrade the nodes where the remaining binlog instances reside, and restart the binlog instances. For more information, see the Upgrade the binlog service section in this topic.

If your binlog task involves only one binlog instance, perform the following steps:

1. Upgrade the node where the binlog instance resides. For more information, see Upgrade the binlog service section in this topic.

2. Run the CREATE BINLOG INSTANCE command to create a binlog instance. For more information about the command, see Instance management.

3. Run the SWITCH MASTER INSTANCE command to switch the new binlog instance to be the primary instance of the current tenant. For more information about the command, see Instance management.

4. If you want to retain only one binlog instance, run the DROP BINLOG INSTANCE command to drop the old one. For more information about the command, see Instance management.

Update the configurations of an existing binlog instance

After a binlog instance is created, most of its configurations cannot be modified. If you want to update its configurations, you must rebuild it.

To reduce impact on your business, you can progressively rebuild the binlog instance by using control commands. For more information about the commands, see Instance management.

1. Run the CREATE BINLOG INSTANCE command to create a binlog instance.

2. Run the SWITCH MASTER INSTANCE command to switch the new binlog instance to be the primary instance of the current tenant.

3. Run the DROP BINLOG INSTANCE command to drop the old binlog instance.