[DOCS-15354] typo on for Atlas pull migration Created: 24/May/22  Updated: 29/Oct/23  Resolved: 25/May/22

Status: Closed
Project: Documentation
Component/s: Atlas
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Minor - P4
Reporter: Mark Baker-Munton Assignee: Julia Malkin
Resolution: Fixed Votes: 0
Labels: cet-captain
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File image-2022-05-24-09-23-16-533.png    
Participants:
Days since reply: 1 year, 37 weeks ago
Story Points: 1

 Description   

The import strategy for live migration (pull) incorrectly states that Cloud/Ops Manager does the pulling.

https://www.mongodb.com/docs/atlas/import/#tools-for-migrating-to-service

 



 Comments   
Comment by Julia Malkin [ 25/May/22 ]

Updated and published:https://www.mongodb.com/docs/atlas/import/

Comment by Julia Malkin [ 24/May/22 ]

https://github.com/10gen/cloud-docs/pull/3310 – please review, Mark. Thank you!

Comment by Julia Malkin [ 24/May/22 ]

Yes, totally agree! Fixed now and in review. Thank you for logging.

Comment by Mark Baker-Munton [ 24/May/22 ]

Typo probably isn't the right description. The issue is saying that "Cloud Manager or Ops Manager pulls data" - this isn't the case. When migrating to Atlas it's Atlas which is pulling the data out from the source cluster not cloud/ops manager.

It's confusing for a client because it suggests that cloud/ops manager is required for the pull live migration when that's not that case. It's only required for the push live migration strategy.

Comment by Julia Malkin [ 24/May/22 ]

mark.baker-munton@mongodb.com Thank you for logging the ticket. This doc organization (around a clear distinction between two types of live migration) and their descriptions have been extensively reviewed. This is the language that we chose to use in the docs and it isn't a typo. Could you please help me understand what you suggest the docs should state instead of the current wording and why stating what we do now is not correct or possible? Thank you!

Generated at Thu Feb 08 08:12:39 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.