[SERVER-19586] Upgrading from 3.0.1 to 3.0.4 in a sharded cluster Created: 24/Jul/15 Updated: 29/Jul/15 Resolved: 27/Jul/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 3.0.1 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Minor - P4 |
| Reporter: | Joey Carmello | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
Hello, I need to upgrade my cluster from 3.0.1 to 3.0.4 and I wanted to get a quick run down on the best way to handle this without causing any problems or inconsistencies. If I added the yum repository to the boxes, could i technically stop the service, run a yum update, then bring the service back up? Or will that wipe my confs, etc. Cheers! |
| Comments |
| Comment by Ramon Fernandez Marina [ 29/Jul/15 ] |
|
jcarmello@madisonlogic.com, we've opened I know that Debian's policy is to keep user-modified files, so I'd be surprised if Yum worked differently. I'd recommend you back up your configuration files before upgrading to be on the safe side. Feel free to vote for Regards, |
| Comment by Ramon Fernandez Marina [ 27/Jul/15 ] |
|
jcarmello@madisonlogic.com, please take a look at the documentation to upgrade minor revisions. Please note that the SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag, where your question will reach a larger audience. See also our Technical Support page for additional support resources. Regards, |