[SERVER-61412] Avoid time-series bucket OID collisions after election Created: 11/Nov/21  Updated: 20/Jan/23

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Dan Larkin-York Assignee: Backlog - Storage Execution Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
is caused by SERVER-61194 Prevent time-series bucket OID reuse ... Closed
Assigned Teams:
Storage Execution
Operating System: ALL
Participants:

 Description   

Our initial time-series bucket ID generation method was susceptible to collisions under conditions of coarse granularity and high bucket generation rates. This was fixed in SERVER-61194, but the fix still allows for the low-probability event that an election could cause further collisions for a period of time. That can be worked around by restarting the new primary. The hope is that we can resolve this in a more graceful way that doesn't require restarting a machine.


Generated at Thu Feb 08 05:52:21 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.