YMatrix
Quick Start
Simulate Time Series Scenarios
Standard Cluster Deployment
Data Modeling
Connecting to The database
Data Writing
Data Migration
Data Query
Scene Application Examples
Federal Query
Maintenance and Monitoring
Global Maintenance
Partition Maintenance
Backup and Restore
Cluster Expansion
Enable Mirroring
Resource Management
Security
Monitoring
Performance Tuning
Troubleshooting
Reference Guide
Tool Guide
Data Type
Storage Engine
Execution Engine
Stream Processing
DR (Disaster Recovery)
Configuration Parameters
Index
Extension
SQL Reference
FAQ
This document introduces the small version upgrade method of MatrixDB 4 database software, as well as the hot upgrade function of the graphic client MXUI.
Small version upgrade refers to upgrading to a new version under the premise that the main version number remains unchanged. For example: upgrade from 4.0.0 to 4.0.2; upgrade from 4.0.0 to 4.1.0.
Below, take the example of upgrading from MatrixDB 4.6.0 to 4.8.0 to introduce detailed steps. In the example, the master node name is mdw.
Obtain the 4.8.0 installation package from the official website, matrixdb-4.8.0.enterprise-1.el7.x86_64.rpm
and copy it to all nodes.
Switch to mxadmin user.
[<username>@mdw ~]$ sudo su - mxadmin
Stop the cluster.
[mxadmin@mdw ~]$ gpstop -af
Upgrade RPM packages with root permissions:
[<username>@mdw ~]$ sudo yum upgrade matrixdb-4.8.0.enterprise-1.el7.x86_64.rpm
Notes!
Do not useyum erase
, otherwise the configuration of the previous version will be deleted.
[<username>@mdw ~]$ sudo systemctl restart matrixdb.supervisor.service
Log in to the Master host and switch to the mxadmin user.
[<username>@mdw ~]$ sudo su - mxadmin
Start the cluster first, add the mars plugin to the shared_preload_libraries
configuration and restart.
[mxadmin@mdw ~]$ gpstart -a
[mxadmin@mdw ~]$ gpconfig -c shared_preload_libraries -v "matrixts,matrixmgr,matrixgate,telemetry,mars"
[mxadmin@mdw ~]$ gpstop -arf
Notes!
The value of shared_preload_libraries needs to be added to MARS based on the original configuration.
If you use the matrixs plug-in and the mars plug-in, connect to the database and upgrade using the following SQL commands:
postgres=# ALTER EXTENSION matrixts UPDATE;
postgres=# ALTER EXTENSION mars UPDATE;
If you use Grafana monitoring, log in to the matrixmgr database, upgrade the matrixmgr plug-in, and reset the acquisition task:
[mxadmin@mdw ~]$ psql -d matrixmgr
matrixmgr=# ALTER EXTENSION matrixmgr UPDATE;
matrixmgr=# SELECT mxmgr_remove_all('local');
matrixmgr=# SELECT mxmgr_deploy('local');
Notes!
4.5.2 and then there is no need to upgrade the matrixmgr plug-in. 4.6.0 and no need to upgrade the mars plug-in again.
Hot upgrade referers to supporting MXUI components to be upgraded independently of the database, allowing you to enjoy the iteration of graphic products faster, with minimal database operations. 
Click the "Upgrade Version" of the mxadmin user option in the lower left corner of the graphic interface. After obtaining the new version of the MXUI executable file, you can perform hot upgrades.