[SERVER-34829] Drop pending reaper must not delete the _dropPendingNamespaces entry until after the drop occurs Created: 03/May/18 Updated: 29/Oct/23 Resolved: 07/May/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Storage |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.6, 4.0.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Dianna Hohensee (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 | ||||||||||||
| Backport Requested: |
v3.6
|
||||||||||||
| Sprint: | Storage NYC 2018-05-07 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Otherwise waiters on the drop will proceed before the drop finishes. Waiters call getEarliestDropOpTime() to determine until what optime they should wait, and getEarliestDropOpTime() looks at _dropPendingNamespaces to determine that. getEarliestDropOpTime() can currently see that _dropPendingNamespaces is empty, when there are still pending-drops to be completed, and return boost::none – or some misinformed answer --, which tells the caller that there's nothing for which to wait. Discovered while testing |
| Comments |
| Comment by Githook User [ 04/Jun/18 ] |
|
Author: {'username': 'DiannaHohensee', 'name': 'Dianna Hohensee', 'email': 'dianna.hohensee@10gen.com'}Message: (cherry picked from commit 8a41a08818c38c4f79a1c4ba2dfe453e8e547dd0) |
| Comment by Githook User [ 07/May/18 ] |
|
Author: {'email': 'dianna.hohensee@10gen.com', 'name': 'Dianna Hohensee', 'username': 'DiannaHohensee'}Message: |