Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-61412

Avoid time-series bucket OID collisions after election

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Backlog
    • Major - P3
    • Resolution: Unresolved
    • None
    • None
    • None
    • None
    • Storage Execution
    • ALL

    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.

      Attachments

        Issue Links

          Activity

            People

              backlog-server-execution Backlog - Storage Execution Team
              dan.larkin-york@mongodb.com Dan Larkin-York
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated: