[SERVER-61194] Prevent time-series bucket OID reuse with coarse granularity Created: 02/Nov/21 Updated: 29/Oct/23 Resolved: 12/Nov/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.2.0, 5.1.2, 5.0.6 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Dan Larkin-York | Assignee: | Dan Larkin-York |
| Resolution: | Fixed | Votes: | 1 |
| 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: |
v5.1, v5.0
|
||||||||||||||||||||||||
| Sprint: | Execution Team 2021-11-15, Execution Team 2021-11-29 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||||||||||
| Description |
|
Currently, when we fill a time-series bucket and roll over to a new one, we can in some cases generate the same bucket OID. This is because we round the timestamp down based on the collection granularity. If we end up with the same rounded timestamp portion of the OID, the rest of the OID may be the same as the previous one. |
| Comments |
| Comment by Githook User [ 24/Nov/21 ] |
|
Author: {'name': 'Dan Larkin-York', 'email': 'dan.larkin-york@mongodb.com', 'username': 'dhly-etc'}Message: |
| Comment by Githook User [ 24/Nov/21 ] |
|
Author: {'name': 'Dan Larkin-York', 'email': 'dan.larkin-york@mongodb.com', 'username': 'dhly-etc'}Message: |
| Comment by Dan Larkin-York [ 23/Nov/21 ] |
|
diego.rodriguez Retrying the inserts may succeed, but there's no guarantee until the backport is released. |
| Comment by Githook User [ 12/Nov/21 ] |
|
Author: {'name': 'Dan Larkin-York', 'email': 'dan.larkin-york@mongodb.com', 'username': 'dhly-etc'}Message: |