Quick onboard
Deployment
Data Modeling
Connecting
Migration
Query
Operations and Maintenance
Common Maintenance
Partition
Backup and Restore
Expansion
Mirroring
Resource Management
Security
Monitoring
Performance Tuning
Troubleshooting
Reference Guide
Tool guide
Data type
Storage Engine
Executor
Stream
DR (Disaster Recovery)
Configuration
Index
Extension
SQL Reference
A minor version upgrade refers to upgrading to a new release while keeping the major version number unchanged.
For example: upgrading from 5.0.0 to 5.0.2, or from 5.0.0 to 5.1.0.
This guide details the upgrade process from YMatrix 5.0.0 to 5.1.0. The master node in this example is named mdw.
Download the 5.1.0 installation package matrixdb5-5.1.0+enterprise-1.el7.x86_64.rpm from the official website and copy it to all cluster nodes.
Switch to the mxadmin user:
[<user_name>@mdw ~]$ sudo su - mxadmin
Stop the cluster:
[mxadmin@mdw ~]$ mxstop -af
Run as the root user: ``
``
Copy the new RPM package to all nodes:
~ scp <local_path> <username>@<server_ip>:<server_path>
Upgrade to the new RPM package as root: ``
``
Note!
Do not useyum erase, as it may remove configuration files from the previous version.
Note!
Due to changes in the installation directory structure, after running theupgradecommand, you must runreinstallto ensure the installation directories are correctly set.
Restart the supervisor service: ``
``
Switch to the mxadmin user:
``
``
Start the cluster:
$ mxstart -a
If the cluster topology has changed in the new database version (e.g., nodes added or removed), and Grafana monitoring is enabled, log in to the matrixmgr database and upgrade the matrixmgr extension. Then reset the data collection tasks:
`` [mxadmin@mdw ~]$ psql -d matrixmgr
matrixmgr=# ALTER EXTENSION matrixmgr UPDATE; matrixmgr=# SELECT mxmgr_remove_all('local'); matrixmgr=# SELECT mxmgr_deploy('local'); ``
