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
YMatrix uses the mxshift tool to perform library data migration operations.
The mxshift tool currently supports the following features:
WHERE
condition._1693981579.png)
If the data migration process is likened by water flowing through the pipeline and the data transmission efficiency is likened by water flow rate, then the water flow rate is often limited to a low value as a whole because of the "narrowest part of the pipeline", resulting in the so-called "single-point bottleneck".
With this in mind, the mxshift tool implements data transfer from the Segment directly to the Segment, eliminating single point bottlenecks that may occur in common migration operations. When the topology of the source cluster and the target cluster are inconsistent, that is, heterogeneous, mxshift can also calculate the optimal mapping scheme based on the number of source cluster segments, the number of target cluster segments, whether the segment is on the same physical machine, etc., to realize automated data migration.
mxshift runs as a configuration file. First, edit the configuration file config.toml
.
Notes!
For the complete configuration file, see mxshift.$ vim config.toml
[database] [database.source] db-database= "testdb" db-host="sdw3" db-password="xxxx" db-port=54322 db-user="mxadmin"
[database.target]
db-database="destdb"
db-host="172.16.100.32"
db-password="yyyy"
db-port=5432
db-user="mxadmin"
[scope] install-dir="/usr/local/greenplum-db-6.7.1"
After you have prepared the TOML file, execute the following command to start mxshift for migration.
$ mxshift -c config_path.toml
> ***Notes!***
For the complete parameters and usage of mxshift, please see [mxshift](/doc/5.2/tools/mxshift).