Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-11051

Fix newest start durable timestamp comparison in aggregate timestamp validation

    • Storage Engines
    • 5
    • 2023-05-16 Chook-n-Nuts Farm
    • v7.0, v5.0, v4.4

      This ticket is created to fix a bug in WiredTiger that was reported in HELP-45345.

      wt verify throws the below error

      ~/mongo/build/debug/third_party/wiredtiger/wt verify  collection-522-4862673103898204079
       [1683327719:569156][29110:0x7fa372b5c6c0], wt, file:collection-522-4862673103898204079.wt, WT_SESSION.verify: [WT_VERB_DEFAULT][ERROR]: int __wt_time_aggregate_validate(WT_SESSION_IMPL *, WT_TIME_AGGREGATE *, WT_TIME_AGGREGATE *, _Bool), 282: aggregate time window has a newest stop durable time after its newest stop time; time aggregate newest durable: (1683215890, 1978)/(1683215891, 5) oldest start: (1683215880, 934)/21632 newest stop (1683215890, 718)/21632: Invalid argument
      [1683327719:569177][29110:0x7fa372b5c6c0], wt, file:collection-522-4862673103898204079.wt, WT_SESSION.verify: [WT_VERB_DEFAULT][ERROR]: int __wt_btree_tree_open(WT_SESSION_IMPL *, const uint8_t *, size_t), 644: unable to read root page from file:collection-522-4862673103898204079.wt: WT_ERROR: non-specific WiredTiger error
      [1683327719:569184][29110:0x7fa372b5c6c0], wt, file:collection-522-4862673103898204079.wt, WT_SESSION.verify: [WT_VERB_DEFAULT][ERROR]: int __verify_filefrag_chk(WT_SESSION_IMPL *, WT_BLOCK *), 434: file ranges never verified: 1
      wt: session.verify: table:collection-522-4862673103898204079: WT_ERROR: non-specific WiredTiger error
      

            Assignee:
            ravi.giri@mongodb.com Ravi Giri
            Reporter:
            ravi.giri@mongodb.com Ravi Giri
            Votes:
            0 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated:
              Resolved:

                Error rendering 'slack.nextup.jira:slack-integration-plus'. Please contact your Jira administrators.