The Improvements mainly improve the synchronization of sharded clusters, especially the synchronization from shards to shards. in earlier versions, the synchronization of two shards was performed by synchronizing Multiple shards to the target mongos, now we have synchronized all parts to each part of the target cluster and automatically migrated the configuration data. After synchronization, the data and distribution of the two clusters are identical. Considerations for sharding cluster synchronization: If domain name configuration is used
The Improvements mainly improve the synchronization of sharded clusters, especially the synchronization from shards to shards. in earlier versions, the synchronization of two shards was performed by synchronizing Multiple shards to the target mongos, now we have synchronized all parts to each part of the target cluster and automatically migrated the configuration data. After synchronization, the data and distribution of the two clusters are identical. Considerations for sharding cluster synchronization: If domain name configuration is used
Improvement
It mainly improves the synchronization of sharding clusters, especially the synchronization from sharding to sharding;
In earlier versions, two shards were synchronized to the target mongos. Now, the shards are synchronized to each shard in the target cluster, and configuration data is automatically migrated. After synchronization, the data and distribution of the two clusters are identical.
Considerations for sharding cluster synchronization: if you use a domain name to configure sharding for each host, the original shard (each host name of the replica set) must be different from the target shard domain name, and there are no restrictions on others, such as shard name.
Synchronize the index of a single table;
Bugfix
- Fixed the synchronization problem to TokuMX, index and user table.
- Fixed the bug where the authentication failed and synchronization continued (the synchronization was not successful) (@ Hisoka-J feedback );
- Fixed a bug reported by Weibo girl @ brief. If semi sync sets -- oplog-s-t, it means to synchronize data for a period of time and the-c parameter is invalid, only the entire database can be synchronized
This bug1.0.3 does not exist before. It appears after 1.4.0 modification.
CHANGE Part
- The incremental synchronization parameter is changed from millisecond to second (All Versions earlier than 1.6.0 are milliseconds );
- Improve the incremental synchronization progress display (Other unchanged) in real-time synchronization, remove the progress bar, instead of displaying the oplog lag time.
- Recovery parameter -- tu, -- tp, that is, specify the target user name and password.
Original article address: MongoDB Data Synchronization tool mongosync 1.6.0 released and new features, thanks to the original author for sharing.