[SERVER-45520] Make writes in MigrationCoordinator::completeMigration retry until success or the local node is stepping down or shutting down Created: 13/Jan/20 Updated: 29/Oct/23 Resolved: 21/Feb/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.4 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | Randolph Tan |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2020-01-27, Sharding 2020-02-10, Sharding 2020-02-24 |
| Participants: |
| Description |
|
Currently, sending remote messages is capped at three retries and local updates areĀ not retried on things such as interrupt due to killOp. This is to ensure that the migration results (abort & commit) are persisted when they are accidentally interrupted by killOp. |
| Comments |
| Comment by Githook User [ 20/Feb/20 ] |
|
Author: {'name': 'Randolph Tan', 'username': 'renctan', 'email': 'randolph@10gen.com'}Message: |