Shulou(Shulou.com)05/31 Report--

This article will explain in detail the principle and use of GaussDB DWS operation and maintenance management function upgrade, the content of the article is of high quality, so the editor will share it with you for reference. I hope you will have a certain understanding of the relevant knowledge after reading this article.

Operation and maintenance management module is the most basic and important part of any software product. It is not only the portal of software products, but also the premise and basis for users to contact and use software products. For example, installation and deployment can let users get started quickly, upgrade can make the product update smoothly, expand the capacity of the product, fault repair can make the product recover quickly, and monitoring alarm can make the product predict in advance or troubleshoot in time. It has higher requirements in usability, ease of use, reliability, maintainability and online operation and maintenance. The principle and use of "upgrade" of important operation and maintenance management function of GaussDB (DWS) are described in detail below.

Preface

Continuous update and evolution is an important behavior of software, and upgrade is an important guarantee of software update. With the continuous introduction of new features and historical problem fixes, software upgrades and patches are particularly important. Upgrades and patches need to meet the following requirements:

Seamless and smooth transition of the software version.

Business disruption is as short as possible, so that it is online.

The user experience is forward compatible.

The database upgrade is more complex than other software upgrades, not only the update of the software itself, but also support the upgrade of the data it manages. Database upgrade needs to consider the following factors:

Software upgrade is the update of the software itself.

Metadata upgrade, that is, the update of the way the software manages data.

Business data upgrade, that is, the upgrade of software-managed data.

With the rapid evolution of database version, upgrade is becoming more and more important, and its reliability, performance, business interruption and ease of use are in urgent need of improvement.

Upgrade and evolution

GaussDB (DWS) upgrade has evolved through several versions, and its performance and reliability have been gradually improved. And provides a variety of upgrade methods for different scenarios. The following is the evolution process:

Full upgrade of large version: the database is rebuilt in the new version, metadata is imported and exported, and mv is used for all business data. It depends on the number of database objects and the size of business data, and the number of business data table files. Deactivated in V1R8.

Upgrade on the spot: replace the binary in place and modify the system table. It depends on the logical size (number of data objects) and physical size (dirty pages of system tables) and the number of databases of system tables.

Small version offline upgrade: stop, replace binary, start the cluster. The business interruption time is the restart time of a cluster.

Small version rolling upgrade: keep the old binaries, install the new binaries in the new directory, scroll to the new binaries according to the component (om_monitor,cm_agent,ETCD,CN,dummy DN,standby DN/GTM/CM,master DN/GTM/CM), and then switch between the active and standby. Two switchover are involved in the whole upgrade process, and the business interruption time depends on the online switchover and CN retry capabilities.

Flash upgrade of the small version: based on the rolling upgrade of the small version, keep the old binaries, install the new binaries in the new directory, first switch management components (om_monitor, cm_agent, ETCD, cm_server), and then switch business components (GTM, CN, DN) at once, and only flash off the business once. DWS is currently in use.

Introduction to the principle of on-site upgrade

At present, the main upgrade method used in 8.0 is in-place upgrade. It has supported the successful upgrade of many clusters offline and public cloud to the new version.

1. Public cloud upgrade process

DWS service upgrade is mainly divided into two parts, management upgrade and tenant upgrade:

The upgrade rollback of the management control plane of each region is mainly completed through the CDK platform, and the components verify their own functions after the upgrade.

Information about upgrading the instance:

Tenant upgrade is operated by SRE on ServiceCM platform, which can be divided into DWS Guest upgrade and database kernel upgrade:

The main process is as follows:

2. Offline updatetool upgrade

By logging in to the UpdateService interface, create an upgrade project and upgrade with one click.

3. Database kernel upgrade process

The database kernel upgrade is done by replacing the binary system and updating the metadata.

It includes 8 phases: initial phase, admission check, environment preparation, downtime, backup, upgrade, update catalog, and submission.

Upgrade performance goals

Upgrade problem location

An overview of the upgrade process log is shown in the following table:

The log of UpdateService is divided into audit log and debug log, as shown in the following table:

About the principle and use of GaussDB DWS operation and maintenance management function upgrade is shared here, I hope the above content can be of some help to you, can learn more knowledge. If you think the article is good, you can share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.