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

Prevent time-series bucket OID reuse with coarse granularity

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 5.2.0, 5.1.2, 5.0.6
    • None
    • None
    • Fully Compatible
    • ALL
    • v5.1, v5.0
    • Execution Team 2021-11-15, Execution Team 2021-11-29

    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.

      Attachments

        Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. SERVER-61412 Avoid time-series bucket OID collisions after election

          • Major - P3 - Major loss of function.
          • Backlog
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-61151 batch->getResult().getStatus() == ErrorCodes::TimeseriesBucketCleared

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              dan.larkin-york@mongodb.com Dan Larkin-York
              dan.larkin-york@mongodb.com Dan Larkin-York
              Votes:
              1 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: