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

Do not increase oldest ID during recovery

    XMLWordPrintable

Details

    • 5
    • Storage - Ra 2022-01-24

    Description

      After turning off backup metadata verification (from WT-8561 analysis) which was causing recovery to not run, I started running a general randomized mirror configuration overnight.

      It hit an assertion:

      t: FAILED: table_verify_mirror/202: base_keyno == table_keyno
      

      What the mirror checking does is walk the standard keys in all the mirror tables. All standard keys should be the same. Then if the keys are the same, it checks the values, which are all updated to the same values in a single transaction.

      In this case, the keys are not the same. The base table, T00001 appears to be missing one since the key numbers are added sequentially:

      [1639577734:619527][22506:0x7f679affd700], t: [WT_VERB_TEMPORARY][INFO]: mirror: mismatch keyno base(table:T00001) 10765 table(table:T00002) 10764
      [1639577734:619536][22506:0x7f679affd700], t: [WT_VERB_TEMPORARY][INFO]: mirror: base key table:T00001: {0000010765.00/opqrstuvwxyzabcdefghijklm}, table key table:T00002: {0000010764.00/opqrstuvw}
      

      Attachments

        1. 8570.diff
          5 kB
        2. WT8570.tar.gz
          56.72 MB

        Issue Links

          Activity

            People

              haribabu.kommi@mongodb.com Haribabu Kommi
              sue.loverso@mongodb.com Susan LoVerso
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: