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

Mirrored table data mismatch

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • WT11.1.0, 6.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • 8
    • Storage Engines - 2022-10-31, Storage Engines - 2022-11-14

      I have a CONFIG that is failing on the current mirror branch (which includes the fix from WT-9522). The first mirrored table is FLCS. The failure has the same signature as WT-9522. I have been able to reproduce it twice (it can take a while - with 5 parallel runs it has hit "overnight").

      The error is:

      mirror: 2236015/2236015 mismatch: table:T00002: {0002236015.00/opqrstuvwxyza}/{0002236015/HMNOPQRSTUVWXYZABCDEFGHIJ} [0x48], table:T
00001: {#}/{0} 
mirror error: base cursor (table 2): dumping to WT_TEST.1/FAIL.pagedump.1
mirror error: table cursor (table 1): dumping to WT_TEST.1/FAIL.pagedump.2
mirror error: base key number 2236015 in table 3: dumping to WT_TEST.1/FAIL.pagedump.3
mirror error: base key number 2236015 in table 4: dumping to WT_TEST.1/FAIL.pagedump.4
t: FAILED: void table_verify_mirror(WT_CONNECTION *, TABLE *, TABLE *, const char *)/322: failures == 0

        1. FAIL.pagedump.1
          0.3 kB
        2. FAIL.pagedump.2
          480 kB
        3. FAIL.pagedump.3
          0.3 kB
        4. FAIL.pagedump.4
          0.3 kB
        5. python_repro.py
          4 kB
        6. rformat5.sh
          1 kB
        7. trace.1703209
          4 kB
        8. trace.411txn
          3.40 MB

            Assignee:
            jie.chen@mongodb.com Jie Chen
            Reporter:
            sue.loverso@mongodb.com Susan LoVerso
            Votes:
            0 Vote for this issue
            Watchers:
            15 Start watching this issue

              Created:
              Updated:
              Resolved: