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

In rollback_to_stable, only check timestamp order if enforced

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • 4.1.3
    • 4.0.4, 4.1.4, WT3.2.0
    • None
    • 3
    • Storage Engines 2018-10-08
    • v4.0

    Description

      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). 

      Attachments

        Issue Links

          Activity

            People

              neha.khatri Neha Khatri
              neha.khatri Neha Khatri
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: