[SERVER-72423] FCBIS will never delete drop-pending tables Created: 29/Dec/22 Updated: 29/Oct/23 Resolved: 06/Jan/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 5.2.0, 6.0.0, 6.1.0, 6.2.0-rc4 |
| Fix Version/s: | 6.0.4, 6.3.0-rc0 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Louis Williams | Assignee: | Matthew Russotto |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | repl-shortlist | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Assigned Teams: |
Replication
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Backport Requested: |
v6.2, v6.0
|
||||||||||||||||||||
| Sprint: | Repl 2023-01-09 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
This is the same class of problem as On startup, we start a "timestamp monitor" on the StorageEngine, which is responsible for completing the second phase of the two-phase drop we employ to drop collections and indexes. After completing a FCBIS, we do not start the timestamp monitor again after re-constructing the storage engine. As a result, we will never actually drop any collections or indexes from the storage engine. This can be fixed permanently by restarting the server. |
| Comments |
| Comment by Githook User [ 06/Jan/23 ] |
|
Author: {'name': 'Matthew Russotto', 'email': 'matthew.russotto@mongodb.com', 'username': 'mtrussotto'}Message: |
| Comment by Githook User [ 06/Jan/23 ] |
|
Author: {'name': 'Matthew Russotto', 'email': 'matthew.russotto@mongodb.com', 'username': 'mtrussotto'}Message: |
| Comment by Githook User [ 06/Jan/23 ] |
|
Author: {'name': 'Matthew Russotto', 'email': 'matthew.russotto@mongodb.com', 'username': 'mtrussotto'}Message: |