Time-series insertBatch should not immediately roll over buckets in the event of a timeForward/timeBackward rollover reason

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      As of SERVER-98477, when we attempt to insert a batch of measurements into a bucket and encounter a rollover reason, we rollover the original bucket and resume inserting into a newly allocated bucket. We should treat rolling over due to time differently - i.e, when we detect that inserting a measurement would cause a bucket to be rolled over, we should check and see if there is an existing "alternate" open bucket that has been marked with a rolloverAction of kArchive or kSoftClose that we can insert into

              Assignee:
              Damian Wasilewicz
              Reporter:
              Damian Wasilewicz
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: