[DOCS-3129] Improve MongoDB 2.6 yum upgrade instructions Created: 11/Apr/14  Updated: 11/Jan/17  Resolved: 28/Apr/14

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: 01112017-cleanup

Type: Improvement Priority: Major - P3
Reporter: James Wahlin Assignee: Ernie Hershey
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-13563 Upgrading from 2.4.x to 2.6.0 via yum... Closed
Participants:
Days since reply: 9 years, 42 weeks, 5 days ago

 Description   

Referring to:

  1. http://docs.mongodb.org/manual/tutorial/install-mongodb-on-red-hat-centos-or-fedora-linux/
  2. Any other MongoDB 2.6 upgrade pages applicable

As of MongoDB 2.4 our yum package names have changed from mongo-10gen* to mongodb-org*

Given the name change the upgrade path would be a package uninstall of 10gen followed by an install of mongodb-org. The problem we encounter here is that the mongod.conf file may be removed and recreated as part of this process. This side-affect may not be apparent to all upgraders. (It should backup this file - but we saw a case where it may not have. We will investigate separately but regardless backup and confirmation of mongod.conf contents is a good practice).

Please add an "upgrade" section to this page and make backing up and confirming contents of the mongod.conf file part of the process.



 Comments   
Comment by Ernie Hershey [ 25/Apr/14 ]

james.wahlin@10gen.com is this still needed now that normal upgrades will work (as of 2.6.1 with SERVER-13563) ?

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