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

Applying operations in recovery encounters unexpected operation type

    • 8
    • Storage Engines 2020-03-09

      Our Evergreen testing of durable history shows a problem. The test that is failing is ftruncate.

      [2020/02/13 11:25:47.282] [1581553547:281976][23451:0x7f53b7f07100], file:oplog.wt, txn-recover: __txn_op_apply, 287: operation apply failed during recovery: operation type 4 at LSN 141/3669120: Invalid argument
      [2020/02/13 11:25:47.282] [1581553547:282030][23451:0x7f53b7f07100], file:oplog.wt, txn-recover: __wt_txn_recover, 764: Recovery failed: Invalid argument
      [2020/02/13 11:25:47.282] [1581553547:282853][23451:0x7f53b7f07100], connection: __wt_cache_destroy, 345: cache server: exiting with 56 pages in memory and 0 pages evicted
      [2020/02/13 11:25:47.282] [1581553547:282868][23451:0x7f53b7f07100], connection: __wt_cache_destroy, 350: cache server: exiting with 824524 image bytes in memory
      [2020/02/13 11:25:47.282] [1581553547:282874][23451:0x7f53b7f07100], connection: __wt_cache_destroy, 353: cache server: exiting with 1589069 bytes in memory
      [2020/02/13 11:25:47.282] [1581553547:282880][23451:0x7f53b7f07100], connection: __wt_cache_destroy, 359: cache server: exiting with 1470464 bytes dirty and 43 pages dirty
      [2020/02/13 11:25:47.285] Parent: compatibility: false, in-mem log sync: true, timestamp in use: true
      

            Assignee:
            haribabu.kommi@mongodb.com Haribabu Kommi
            Reporter:
            alexander.gorrod@mongodb.com Alexander Gorrod
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: