[SERVER-74185] Support for cleanup in Recoverable Sharding DDL Coordinator Created: 20/Feb/23 Updated: 29/Oct/23 Resolved: 10/Mar/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Antonio Fuschetto | Assignee: | Antonio Fuschetto |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Sharding EMEA 2023-03-06, Sharding EMEA 2023-03-20 | ||||||||
| Participants: | |||||||||
| Description |
|
The Sharding DDL Coordinator offers a facility to trigger a function at the end of every phase. This can be used to determine if the phase should re-executed based on some conditions, but NOT to rollback actions because the mechanism is not fault-tolerant (i.e., in case of any error while this procure is running would cause the entire phase to be re-executed from scratch). The goal of this ticket is to provide a recoverable infrastructure to run a procedere at the end of each phase, so that this can be possibly used to rollback actions completed in the current phase. |
| Comments |
| Comment by Githook User [ 09/Mar/23 ] |
|
Author: {'name': 'Antonio Fuschetto', 'email': 'antonio.fuschetto@mongodb.com', 'username': 'afuschetto'}Message: |