[DOCS-11149] Be more clear about the impact of configuration changes on an Atlas cluster Created: 21/Dec/17 Updated: 29/Oct/23 Resolved: 30/Jan/18 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Atlas |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Joanna Cheng | Assignee: | Robert Justice (Inactive) |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 6 years, 2 weeks ago | ||||
| Epic Link: | DOCSP-1743 | ||||
| Description |
|
https://docs.atlas.mongodb.com/scale-cluster/#migration-downtime-and-performance-impact This seems a bit too soft Suggest something like: Not that exact wording, but something along those lines |
| Comments |
| Comment by Robert Justice (Inactive) [ 31/Jan/18 ] |
|
Ravind merged! |
| Comment by Shannon Bradshaw (Inactive) [ 21/Dec/17 ] |
|
joanna.cheng, from reading the HELP ticket, it looks like the issue is that IOPS change requested triggered a special case for which AWS would not permit a change to the instance. So, in order to satisfy the customer request, we had to migrate their cluster to new instances. Is that a correct read of this issue? If so, I believe we should document (as best we can) the scenarios that will trigger a migration and provide some guidance to the reader as to how long this might take (i.e. hours, not minutes). That should provide them with the ability to plan better, I believe. Thoughts on that? |