Size-based truncation shouldn't issue excessively large truncates

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Works as Designed
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Integration
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      https://jira.mongodb.org/browse/SERVER-130700 was implemented for time-based truncation to limit the size of a single truncate to N hours.

      Investigate whether this logic is needed for size-based truncation, validating with testing.

      We may want to investigate setting an upper limit on truncate marker size to avoid truncates that cannot be handled by WT.

            Assignee:
            Erin Liang
            Reporter:
            Anna Veselova
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: