[DOCS-2923] Comment on 2.6 upgrade document Created: 17/Mar/14  Updated: 17/Mar/14  Resolved: 17/Mar/14

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: v1.3.2, mongodb-2.6

Type: Improvement Priority: Minor - P4
Reporter: Linda Qin Assignee: Kay Kim (Inactive)
Resolution: Done Votes: 0
Labels: sprint-slipstream
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 9 years, 48 weeks, 2 days ago

 Description   

http://docs.mongodb.org/master/release-notes/2.6-upgrade

  1. Some "2.5.x" are not updated to 2.6
    For example:

    Upgrade/Downgrade Path:
    Once upgraded to MongoDB 2.5.x, you cannot downgrade to a version earlier than MongoDB 2.4 via any downgrade path; i.e. you can only downgrade to MongoDB 2.4. If you have text indexes, you can only downgrade to MongoDB 2.4.9 or higher.

  2. It would be nice if we can also clarify the roles required for this adminitrator user.

    Ensure that at least one user exists in the admin database before upgrading to MongoDB 2.6.

  • 2.2 legacy user should have read/write permission in the admin database.
  • 2.4 user should have userAdminAnyDatabase roles in the admin database.


 Comments   
Comment by Githook User [ 17/Mar/14 ]

Author:

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

Message: DOCS-2923 add user role for upgrading to 2.6 auth model
Branch: master
https://github.com/mongodb/docs/commit/215307a939e8e9b0a4c535456e4b4a5968baef09

Generated at Thu Feb 08 07:44:35 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.