[SERVER-29812] RangeDeleter unnecessarily waits for 'majority' write concern Created: 23/Jun/17 Updated: 30/Oct/23 Resolved: 28/Feb/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.2.14, 3.4.4 |
| Fix Version/s: | 3.4.14 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Kevin Pulo |
| 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 2018-02-26, Sharding 2018-03-12 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
The range deleter waits for replication on two occasions:
This second majority wait is completely unnecessary. The migration recipient side can keep going without attempting a majority write until the very end, after all documents have been transferred. As part of fixing this bug, we should consider the following:
|
| Comments |
| Comment by Githook User [ 28/Feb/18 ] |
|
Author: {'email': 'kevin.pulo@mongodb.com', 'name': 'Kevin Pulo', 'username': 'devkev'}Message: |
| Comment by Kaloian Manassiev [ 21/Feb/18 ] |
|
kevin.pulo, I agree with your comments. With the changes we are currently doing to optimize the speed of migrations, I don't think we need to look into the second part yet. I opened |
| Comment by Kevin Pulo [ 21/Feb/18 ] |
This feels like
Since this would be a migration-related change, rather than range deleter related — and also possibly relevant to master, not just v3.4 — I think this would be better considered on its own SERVER ticket. Let me know if you'd still like me to look into this aspect on this ticket. |
| Comment by Kaloian Manassiev [ 15/Nov/17 ] |
|
Yes, this is no longer a problem in 3.6, but I would like to have it fixed in 3.4 because it will improve the speed of migrations. |
| Comment by Dianna Hohensee (Inactive) [ 15/Nov/17 ] |
|
This ticket relates to the old RangeDeleter, which has since been replaced by a new CollectionRangeDeleter. kaloian.manassiev, can we close this, or are you thinking of a v3.4 backport? |