[SERVER-46892] two phase index build allowed to start on drop-pending collection Created: 16/Mar/20 Updated: 29/Oct/23 Resolved: 03/Apr/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.4.0-rc2, 4.7.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Benety Goh | Assignee: | Benety Goh |
| 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: |
v4.4
|
||||||||||||||||
| Sprint: | Execution Team 2020-04-06, Execution Team 2020-04-20 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 44 | ||||||||||||||||
| Description |
|
A collection drop and index creation on a primary node may interleave in a way that causes a two phase index build to start the index build on a drop-pending collection namespace (db.system.drop.*). This is partly due to the checks, introduced in This bug affects configurations that disable majority reads or use the {ephemeralForTest}storage engine. |
| Comments |
| Comment by Githook User [ 13/Apr/20 ] |
|
Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}Message: (cherry picked from commit cf571d9224eff2b613756af87fb0e2974192138a) |
| Comment by Githook User [ 13/Apr/20 ] |
|
Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}Message: (cherry picked from commit 89d74003c2e88b2d3a0fb4aaac7ec6b5e4dd9ad5) |
| Comment by Githook User [ 02/Apr/20 ] |
|
Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}Message: |
| Comment by Githook User [ 02/Apr/20 ] |
|
Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}Message: |