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

Enable the assertion that the durable_timestamp is newer than or equals the commit timestamp.

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: WT3.2.0, 4.1.11
    • Component/s: None
    • Labels:
      None
    • Story Points:
      2
    • Sprint:
      Storage Engines 2019-04-22

      Description

      For a committed transaction, its durable timestamp should always be greater than or equal to its commit timestamp:

      +                       WT_ASSERT(session,
      +                           (prepare_state == WT_PREPARE_INPROGRESS ||
      +                           durable_timestamp >= las_timestamp));

      This assertion fails in test_schema_abort with the following state of the involved parameters:

      (gdb) p prepare_state
      $1 = 3 '\003' (WT_PREPARE_RESOLVED)
      (gdb) p durable_timestamp
      $2 = 46426
      (gdb) p las_timestamp
      $3 = 46428

      Since test_schema_abort does not explicitly set the durable timestamp, its durable timestamp should not have diverged from the commit timestamp. Identify the cause of this divergence and then enable the assertion.

        Attachments

          Activity

            People

            Assignee:
            vamsi.krishna Vamsi Boyapati
            Reporter:
            neha.khatri Neha Khatri
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: