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

Test control.max.time rounding's effect on DISTINCT_SCAN for TS Last Point

    XMLWordPrintableJSON

Details

    • Icon: Question Question
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None

    Description

      james.wahlin left this comment on the technical design doc:

      I know we round the value stored in bucket _id to second granularity. We should make sure we don't also round control.min.time and control.max.time. If we do then it is possible we could have 2 buckets starting at the same time with no guarantee that the first one we look at has the most recent or oldest point.

      If there is indeed rounding being done on control.max.time then the DISTINCT_SCAN may return the one of several "equal-max-time" buckets which actually has a slightly older value than the true last.

      Attachments

        Activity

          People

            steve.tarzia@mongodb.com Steve Tarzia
            steve.tarzia@mongodb.com Steve Tarzia
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: