[SERVER-58896] Fix metaField-only time-series updates with concurrent collection drops Created: 27/Jul/21 Updated: 29/Oct/23 Resolved: 05/Aug/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: | Alison Lu (Inactive) | Assignee: | Alison Lu (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-08-09 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 144 | ||||||||||||
| Description |
|
Currently, locks are not held while time-series queries and updates 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 update executes. To solve this, all the metaField related logic should be moved to performSingleUpdateOp() in write_ops_exec.cpp. |
| Comments |
| Comment by Githook User [ 07/Oct/21 ] |
|
Author: {'name': 'Alison Lu', 'email': 'alison.lu@mongodb.com', 'username': 'alison-lu'}Message: (cherry picked from commit 1f4dbf3dde9d6b3da361a4ec3a27647920d75a64) |
| 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 [ 05/Aug/21 ] |
|
Author: {'name': 'Alison Lu', 'email': 'alison.lu@mongodb.com', 'username': 'alison-lu'}Message: |