[SERVER-56271] Investigate time-series bucket updates where the bucket is not found Created: 22/Apr/21 Updated: 06/Dec/22 Resolved: 29/Apr/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Gregory Noma | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Storage Execution
|
||||||||||||||||
| Sprint: | Execution Team 2021-05-31 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
We currently have special handling for the case where we try to perform time-series inserts by updating an existing bucket, but the bucket isn't found. However, after We should look into the cases where this still happens and either fix them or determine that these cases are safe. If we are able to eliminate this behavior, we can also remove the special handling for this scenario. |