In rollback_to_stable, only check timestamp order if enforced

XMLWordPrintableJSON

    • Storage Engines 2018-10-08
    • 3
    • v4.0

      An  Evergreen test that exercises rollback to stable on __mdb_catalog.wt fires the following assertion:

      2018-09-05T18:43:55.612+0000 E STORAGE [rsBackgroundSync] WiredTiger error (0) [1536173035:612600][17280:2007970688], file:_mdb_catalog.wt, WT_CONNECTION.rollback_to_stable: __txn_abort_newer_update, 134: upd == first_upd Raw: [1536173035:612600][17280:2007970688], file:_mdb_catalog.wt, WT_CONNECTION.rollback_to_stable: __txn_abort_newer_update, 134: upd == first_upd
2018-09-05T18:43:55.612+0000 E STORAGE [rsBackgroundSync] WiredTiger error (0) [1536173035:612600][17280:2007970688], file:_mdb_catalog.wt, WT_CONNECTION.rollback_to_stable: __wt_abort, 30: aborting WiredTiger library Raw: [1536173035:612600][17280:2007970688], file:_mdb_catalog.wt, WT_CONNECTION.rollback_to_stable: __wt_abort, 30: aborting WiredTiger library
2018-09-05T18:43:55.780+0000 F - [rsBackgroundSync] Got signal: 22 (SIGABRT).

            Assignee:
            Neha Khatri (Inactive)
            Reporter:
            Neha Khatri (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: