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

Make change collection writes ordered by timestamp instead of grouped by tenantId

    • Replication
    • Fully Compatible
    • v8.0
    • Repl 2024-04-01, Repl 2024-04-15

      To address serverless change collection test failure.

      Grouping by tenantID means the entries in the storage transaction are not necessarily order by timestamp, and we may hit a WT assertion:

      [js_test:write_to_change_collection] d20791| 2024-04-04T08:50:48.024+00:00 E  WT       22435   [S] [ReplWriterWorker-0] "WiredTiger error message","attr":
      {
          error: 22,
          message: {
              ts_sec: 1712220648,
              ts_usec: 24463,
              thread: "15548:0xffff3b09a610",
              session_name: "WT_SESSION.timestamp_transaction_uint",
              category: "WT_VERB_DEFAULT",
              category_id: 12,
              verbose_level: "ERROR",
              verbose_level_id: -3,
              msg: "__wt_txn_validate_commit_timestamp:545:commit timestamp (1712220648, 9) older than the first commit timestamp (1712220648, 10) for this transaction",
              error_str: "Invalid argument",
              error_code: 22
          }
      } 

            Assignee:
            wenbin.zhu@mongodb.com Wenbin Zhu
            Reporter:
            wenbin.zhu@mongodb.com Wenbin Zhu
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: