[SERVER-46183] Only wait for replication once at the end of range deletion Created: 14/Feb/20 Updated: 29/Oct/23 Resolved: 18/Feb/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Matthew Saltz (Inactive) | Assignee: | Matthew Saltz (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Sharding 2020-02-24 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
We now wait for replication after each batch of documents deleted, instead of once at the end, as we did in 4.2. This was done intentionally knowing that deletion would be delayed some with the benefit of simplifying the deleter logic, but on second thought it doesn't simplify much and we think it's better to just do it once at the end, so we should do that. |
| Comments |
| Comment by Githook User [ 18/Feb/20 ] |
|
Author: {'name': 'Matthew Saltz', 'username': 'saltzm', 'email': 'matthew.saltz@mongodb.com'}Message: |
| Comment by Matthew Saltz (Inactive) [ 18/Feb/20 ] |