2 個答案
- 最新
- 最多得票
- 最多評論
4
There is no need to upgrade your MongoDB version, DMS supports MongoDB version 3.0+. The documentation at https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Source.MongoDB.html merely states that support for MongoDB 4.2 and 4.4 was added in DMS version 3.4.5.
已回答 1 年前
3
you'll need to consider alternative methods
- Upgrade your MongoDB instances to a supported version before using AWS DMS
- Perform a live migration using a custom script or tool Write a custom script or use a third-party tool (e.g., Apache Nifi, Talend, or custom-built solutions) to perform a live migration of the data from your MongoDB 3.2.x instances to AWS DocumentDB.
nice info bro. cheers.
相關內容
- 已提問 6 個月前
- 已提問 1 年前
AWS 官方已更新 1 年前- AWS 官方已更新 9 個月前
- AWS 官方已更新 8 個月前
- AWS 官方已更新 2 年前
ya, but it strange since I can't connect to mongodb 3.2.xx from AWS DMS. Already reachable via AWS Reachability Analysis, BindIP -> I've setup it already. So I assume it because of wire protocol from mongodb version 3.2.xx.
MongoServerSelectionError: Server at xxxxxx:27017 reports maximum wire version 4, but this version of the Node.js Driver requires at least 6 (MongoDB 3.6). I event can't connect from other server. :)