Investigate and reduce excessive "read timestamp less than oldest timestamp" WT logs

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Test Format
    • None
    • Storage Engines - Foundations
    • SE Foundations - 2026-01-02
    • 5

      Observing a high volume of logs that are creating noise. This makes it difficult to debug relevant issues.

      2025/11/23 20:26:41.197] 0x529d3fca2878:[1763947601:197258][156593:0xffff887edbc0], t, WT_SESSION.timestamp_transaction_uint: [WT_VERB_TIMESTAMP][NOTICE]: read timestamp (0, 1698526) less than the oldest timestamp (0, 1699052)

      Acceptance Criteria:
      The specific log entries are no longer spamming the logs, Or are reduced to a negligible amount.

            Assignee:
            [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            Sid Mahajan
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: