[DOCS-9969] Cloud / Ops Manager: the upgrade/downgrade order must be followed if executed for individual components Created: 06/Mar/17 Updated: 08/Jul/17 Resolved: 14/Jun/17 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Cloud Manager, Ops Manager |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Dmitry Ryabtsev | Assignee: | Anthony Sansone (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 6 years, 31 weeks, 4 days ago |
| Epic Link: | OM Install |
| Story Points: | 0.2 |
| Description |
|
Some users may prefer executing upgrade with Automation but for individual components of the sharded cluster, in a controlled manner. It would be nice to have this option covered in the documentation. The documentation should clearly say that the order of the upgrade steps must be followed - i.e. config servers -> shards -> mongos. |
| Comments |
| Comment by Githook User [ 08/Jul/17 ] |
|
Author: {u'username': u'atsansone', u'name': u'Tony Sansone', u'email': u'tony.sansone@mongodb.com'}Message: ( |
| Comment by Githook User [ 08/Jul/17 ] |
|
Author: {u'username': u'atsansone', u'name': u'Tony Sansone', u'email': u'tony.sansone@mongodb.com'}Message: ( |