Avoid time-series bucket OID collisions after election

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              [DO NOT USE] Backlog - Storage Execution Team
              Reporter:
              Dan Larkin-York
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated: