[SERVER-58519] Fix metaField-only time-series deletes with concurrent collection drops Created: 14/Jul/21 Updated: 29/Oct/23 Resolved: 27/Jul/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.4, 5.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Kris Satya (Inactive) | Assignee: | Kris Satya (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 | ||||||||||||
| Backport Requested: |
v5.0
|
||||||||||||
| Sprint: | Execution Team 2021-07-26, Execution Team 2021-08-09 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Currently, locks are not held while time-series queries are parsed to replace the metaField with "meta" in write_commands.cpp and while retrieving the metaField in write_ops_exec.cpp. This may lead to concurrency issues where the collection may be dropped or replaced with another collection before the delete executes. To solve this, all the metaField related logic should be moved to the |
| Comments |
| Comment by Githook User [ 07/Oct/21 ] |
|
Author: {'name': 'Kris Satya', 'email': 'kris.satya@mongodb.com', 'username': 'KoolCards'}Message: (cherry picked from commit f72311328f8b803546a0fadac3db5f213f9990c9) |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! |
| Comment by Githook User [ 27/Jul/21 ] |
|
Author: {'name': 'Kris Satya', 'email': 'kris.satya@mongodb.com', 'username': 'KoolCards'}Message: |