- 最新
- 投票最多
- 评论最多
Addition: We found this new MongoDB endpoint setting at DMS 3.4.7 release notes (https://docs.aws.amazon.com/dms/latest/userguide/CHAP_ReleaseNotes.html):
FullLoadNoCursorTimeout => "MongoDB endpoint setting FullLoadNoCursorTimeout specifies NoCursorTimeout for the full load cursor. NoCursorTimeout is a MongoDB connection setting that prevents the server from closing the cursor if idle."
Unfortunately adding it to an existing endpoint as an "Endpoint settings" using the AWS console seems not to work. So we tried to set as an "Extra connection attribute" like this: "authMechanism=DEFAULT;authSource=vdstest;authType=PASSWORD;extractDocId=true;FullLoadNoCursorTimeout=true;nestingLevel=NONE;socketTimeoutMS=3600000;" This has no effect - After about 10 minutes of full loading the above described error occurs: "Connection closed by peer"
So my second question is: How can we set "FullLoadNoCursorTimeout" for an MongoDB endpoint?
相关内容
- AWS 官方已更新 2 年前
- AWS 官方已更新 8 个月前
- AWS 官方已更新 2 年前
- AWS 官方已更新 2 年前
The way you specified FullLoadNoCursorTimeout, but it might not work properly because of the sharded configuration on the source endpoint. You should be able to get a list of cursors and their type to confirm this, if you are on MongoDB 4.2 or later check the documentation: https://www.mongodb.com/docs/manual/reference/operator/aggregation/currentOp/ . For DMS, you could try a different approach, which is to use segmentation for the bigger collection. See this blog: https://aws.amazon.com/blogs/database/use-segmentation-to-improve-performance-for-large-mongodb-and-amazon-documentdb-migrations-in-aws-dms/