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
Monitoring
Performance Tuning
Troubleshooting
Reference Guide
Tool Guide
Data Type
Storage Engine
Execution Engine
Configuration Parameters
SQL Reference
FAQ
Recovers a YMatrix database system.
The mxrecover tool uses a failback mechanism to recover failed nodes in the cluster.
| Option | Description |
|---|---|
| -c or --db-cluster-id |
Specifies the target database cluster ID. If omitted, the default value mdw is used as the cluster ID. |
| -F or --force-full-resync | Forces a full resynchronization of Primary/Master data to repair a damaged Mirror/Standby. |
| -r or --rebalance | After recovering failed Segments/Masters, restores all Segments/Masters within each shard to their original Primary/Master or Mirror/Standby roles as defined at initial database setup. |
| -q | Runs in quiet mode. Suppresses command output on the terminal, but logs are still written to the log file. |
| -h or --help | Displays help information. |
| -Q or --query | Periodically prints recovery progress. |
Note!
Bothmxrecoverandmxrecover -Fonly initiate recovery requests and do not wait for completion. The recovery process runs in the background, allowing you to continue other client operations without blocking. However, no progress or final status is displayed automatically. Usemxrecover -Qormxrecover --queryto manually check the recovery status.
Note!
Whenmxrecoveris run with no options or only the-coption, an incremental recovery is initiated.
Recover a failed Segment/Master:
mxrecoverPerform a full recovery of a failed Segment/Master:
mxrecover -F
#or
mxrecover --force-full-resyncRestore Segment/Master roles:
mxrecover -r
#or
mxrecover --rebalanceNote!
YMatrix 5 introduces a new database architecture and uses themxrecovertool for cluster recovery. It is incompatible withgprecoverseg. In earlier versions, use thegprecoversegtool.