[DOCS-587] Need documentation on what Rollback each phases are doing Created: 08/Oct/12 Updated: 29/Nov/12 Resolved: 11/Oct/12 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Andre de Frere | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 11 years, 18 weeks, 6 days ago | ||||
| Description |
|
While we do report in the logs that rollback is going through various phases, we do not have any documentation telling customers what these statuses mean. For example we will output 'rollback 1', 'rollback 2' etc into the logs. If a customer knew what was happening in each of these steps, they would be able to make informed choices about what to do when one of these steps appears to fail. |
| Comments |
| Comment by Sam Kleinman (Inactive) [ 11/Oct/12 ] |
|
doesn't make sense to document, given earlier discussion. Feel free to reopen if it makes sense to document this information. |
| Comment by Sam Kleinman (Inactive) [ 09/Oct/12 ] |
|
I'm uncertain about this: 1. It strikes me that if a rollback fails at any point for internal reasons the only real option is to resync, regardless of a failure at 2 or at step 3? Alternately you could restart the rolling back secondary in standalone mode, get data out of it, and then resync: again documentation of what happens in step 3 vs step 4 doesn't really matter here. 2. This kind of behavior could (and likely will change), and the procedure may eventually include additional steps that we will have a hard time keeping up with. Which may be particularly difficult given the above. Cheers, |