[DOCS-10986] Create landing page on migration for users still running MMAPv1 Created: 06/Nov/17  Updated: 29/Oct/23  Resolved: 13/Apr/18

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

Type: Task Priority: Major - P3
Reporter: Ian Whalen (Inactive) Assignee: Kay Kim (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to DOCS-11097 Docs for SERVER-31954: Mark MMAPv1 st... Closed
Participants:
Days since reply: 5 years, 43 weeks, 5 days ago
Epic Link: DOCS: 4.0 Server
Story Points: 1

 Description   

This landing page should be titled: "Migrate from MMAPv1 to WiredTiger Storage Engine" or something like that. It should include:



 Comments   
Comment by Kay Kim (Inactive) [ 13/Apr/18 ]

Should be out now.

Comment by Kay Kim (Inactive) [ 13/Apr/18 ]

Thanks much!

Comment by Githook User [ 10/Apr/18 ]

Author:

{'email': 'kay.kim@10gen.com', 'name': 'kay', 'username': 'kay-kim'}

Message: DOCS-10986,DOCS-11097: mmapv1 deprecation
Branch: master
https://github.com/mongodb/docs/commit/409a24d94fbbe2046f9364b1c05d726d8e5dc6cd

Comment by Kay Kim (Inactive) [ 15/Mar/18 ]

Will do. thanks.

Comment by Ian Whalen (Inactive) [ 15/Mar/18 ]

milkie is out on vacation so I'm paging geert.bosch into this conversation to answer as needed.

kay.kim, you should also probably switch up the assigned reviewers with Geert in place of Eric.

Comment by Neha Khatri [ 21/Feb/18 ]

kay.kim This is to keep you updated that per the recent decisions, MMAPV1 is deprecated in 4.0 and will be removed in 4.2. The versions have changed, in case this information is required for documentation update.

Comment by Kay Kim (Inactive) [ 30/Nov/17 ]

I've created:

dochub.mongodb.org/core/deprecated-mmapv1

This will for now point to https://docs.mongodb.com/master/release-notes/

Sometime in January, as we get ready for 3.8, it'll point to actual place with mmapv1 deprecation.

Comment by Neha Khatri [ 28/Nov/17 ]

kay.kim Yes, server team needs a permanent dochub link which need not change when the real page gets created.

Comment by Eric Milkie [ 28/Nov/17 ]

That gives us everything we need, so its OK by me.

Comment by Ian Whalen (Inactive) [ 28/Nov/17 ]

Seems to work for me, but I would want neha.khatri and milkie to confirm that's OK.

Comment by Kay Kim (Inactive) [ 28/Nov/17 ]

So, do you want a dochub link? In which case, it could point to a missing page, but you all won't have to change the link.
When the destination actually exists, the docs team just updates what the dochub link points to, and so, wouldn't require a change from server team on their side.

Comment by Ian Whalen (Inactive) [ 28/Nov/17 ]

kay.kim neha.khatri What do you think about possibly putting up a stub docs page with a dedicated link so that the Server team can be unblocked with updating our logs with a link to that page?

Comment by Steve Renaker (Inactive) [ 09/Nov/17 ]

Scope document: https://docs.google.com/document/d/1xNJHmS9jAB62MTu7LvJeYl6T1igafFVdw7Fsfb6V7gI/edit#heading=h.sye21yee6q34

Comment by Asya Kamsky [ 06/Nov/17 ]

kay.kim made some comments in the related scope document, cc'ing her here.

Comment by Ian Whalen (Inactive) [ 06/Nov/17 ]

Hey Steve, I think asya will be better equipped to handle those questions. For context: we are deprecating MMAPv1 in the upcoming 3.8 release and will need a single URL to direct users to, regardless of whether they're running a standlone, replset, etc.

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