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

test/format ENOENT on WiredTiger.turtle.set file

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: WT2.7.0
    • Labels:
      None
    • # Replies:
      24
    • Last comment by Customer:
      true

      Description

      Running test/format on the CONFIG for WT-2169 I hit this failure after 18 iterations:

      [1444767452:413810][9307:0x7f421affd700], t, file:WiredTiger.wt, WT_SESSION.checkpoint: RUNDIR/WiredTiger.turtle.set: No such file or directory
      

        Issue Links

          Activity

          Hide
          xgen-internal-githook Githook User added a comment -

          Author:

          {u'username': u'sueloverso', u'name': u'sueloverso', u'email': u'sue@mongodb.com'}

          Message: Merge pull request #2266 from wiredtiger/wt-2170

          WT-2170 Move metadata read uncommitted to search
          Branch: develop
          https://github.com/wiredtiger/wiredtiger/commit/91ee6a2fc7392a4a9e2c8b57c5319ede0f98b44e

          Show
          xgen-internal-githook Githook User added a comment - Author: {u'username': u'sueloverso', u'name': u'sueloverso', u'email': u'sue@mongodb.com'} Message: Merge pull request #2266 from wiredtiger/wt-2170 WT-2170 Move metadata read uncommitted to search Branch: develop https://github.com/wiredtiger/wiredtiger/commit/91ee6a2fc7392a4a9e2c8b57c5319ede0f98b44e
          Hide
          xgen-internal-githook Githook User added a comment -

          Author:

          {u'username': u'michaelcahill', u'name': u'Michael Cahill', u'email': u'michael.cahill@mongodb.com'}

          Message: WT-2170 Application metadata cursors expect read-uncommitted semantics.
          Branch: develop
          https://github.com/wiredtiger/wiredtiger/commit/b3dd263d30a6e1504a17d845f07210044569a386

          Show
          xgen-internal-githook Githook User added a comment - Author: {u'username': u'michaelcahill', u'name': u'Michael Cahill', u'email': u'michael.cahill@mongodb.com'} Message: WT-2170 Application metadata cursors expect read-uncommitted semantics. Branch: develop https://github.com/wiredtiger/wiredtiger/commit/b3dd263d30a6e1504a17d845f07210044569a386
          Hide
          xgen-internal-githook Githook User added a comment -

          Author:

          {u'username': u'michaelcahill', u'name': u'Michael Cahill', u'email': u'michael.cahill@mongodb.com'}

          Message: Merge pull request #2275 from wiredtiger/WT-2170-metadata-read-uncommitted

          WT-2170 Application metadata cursors expect read-uncommitted semantics.
          Branch: develop
          https://github.com/wiredtiger/wiredtiger/commit/3868d0b8e1066eb7a6bb47cc3ce4ba20e083a4f3

          Show
          xgen-internal-githook Githook User added a comment - Author: {u'username': u'michaelcahill', u'name': u'Michael Cahill', u'email': u'michael.cahill@mongodb.com'} Message: Merge pull request #2275 from wiredtiger/ WT-2170 -metadata-read-uncommitted WT-2170 Application metadata cursors expect read-uncommitted semantics. Branch: develop https://github.com/wiredtiger/wiredtiger/commit/3868d0b8e1066eb7a6bb47cc3ce4ba20e083a4f3
          Hide
          xgen-internal-githook Githook User added a comment -

          Author:

          {u'username': u'michaelcahill', u'name': u'Michael Cahill', u'email': u'michael.cahill@mongodb.com'}

          Message: Merge pull request #2275 from wiredtiger/WT-2170-metadata-read-uncommitted

          WT-2170 Application metadata cursors expect read-uncommitted semantics.
          Branch: develop
          https://github.com/wiredtiger/wiredtiger/commit/3868d0b8e1066eb7a6bb47cc3ce4ba20e083a4f3

          Show
          xgen-internal-githook Githook User added a comment - Author: {u'username': u'michaelcahill', u'name': u'Michael Cahill', u'email': u'michael.cahill@mongodb.com'} Message: Merge pull request #2275 from wiredtiger/ WT-2170 -metadata-read-uncommitted WT-2170 Application metadata cursors expect read-uncommitted semantics. Branch: develop https://github.com/wiredtiger/wiredtiger/commit/3868d0b8e1066eb7a6bb47cc3ce4ba20e083a4f3
          Hide
          xgen-internal-githook Githook User added a comment -

          Author:

          {u'username': u'michaelcahill', u'name': u'Michael Cahill', u'email': u'michael.cahill@mongodb.com'}

          Message: WT-2170 Restore visible_all semantics if we try to check visibility without a snapshot.

          There are various internal checks (e.g., checking tombstone visibility during tree walks, and during eviction of dirty trees prior to an exclusive operation like drop) where we don't have a transactional snapshot, but the isolation level may be set read-committed or higher. The isolation level is irrelevant to these checks: we used to have a special "eviction" isolation level to avoid these issues.

          This change restores that semantic: if we attempt a visibilty check without a snapshot, fall back to only making stable updates visible.
          Branch: develop
          https://github.com/wiredtiger/wiredtiger/commit/63e7e056393313634d35ab04cb69503923ec6ac0

          Show
          xgen-internal-githook Githook User added a comment - Author: {u'username': u'michaelcahill', u'name': u'Michael Cahill', u'email': u'michael.cahill@mongodb.com'} Message: WT-2170 Restore visible_all semantics if we try to check visibility without a snapshot. There are various internal checks (e.g., checking tombstone visibility during tree walks, and during eviction of dirty trees prior to an exclusive operation like drop) where we don't have a transactional snapshot, but the isolation level may be set read-committed or higher. The isolation level is irrelevant to these checks: we used to have a special "eviction" isolation level to avoid these issues. This change restores that semantic: if we attempt a visibilty check without a snapshot, fall back to only making stable updates visible. Branch: develop https://github.com/wiredtiger/wiredtiger/commit/63e7e056393313634d35ab04cb69503923ec6ac0

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Days since reply:
                1 year, 34 weeks, 2 days ago
                Date of 1st Reply: