[SERVER-49314] Startup warning when rollback files exist Created: 03/Jul/20 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Nic Cottrell | Assignee: | Backlog - Replication Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Replication
|
| Participants: | |
| Case: | (copied to CRM) |
| Description |
|
While rollback events will be logged when they happen, it might be missed on a complex, busy cluster. In order for the existence of rollback files to be detected easily by existing tools, we should report their presence as a startup warning. |
| Comments |
| Comment by Jonathan Streets (Inactive) [ 07/Jul/20 ] |
|
evin.roesle do you have any advice on this one ? thanks. jon. |