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

Unlock when sleeping to allow other log threads to make progress

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.0.5, 4.1.5, 3.6.10, WT3.2.0
    • Component/s: None
    • Labels:
      None
    • Sprint:
      Storage Engines 2018-10-22, Storage Engines 2018-11-05
    • Backport Requested:
      v4.0, v3.6

      Description

      When starting with a huge number of threads, timestamp_abort hangs and eventually aborts in the logging code. The code cannot find a free log slot for 10 seconds and then dumps out all the log slot information.

      The large increase in the maximum number of threads in the test is from WT-3995. This failure on kodkod at http://build.wiredtiger.com:8080/job/wiredtiger-test-recovery-stress/52365/console had this configuration:

      test_timestamp_abort -h WT_TEST.timestamp-abort -T 195 -t 10
      

        Attachments

        1. log-dump.txt
          106 kB
        2. thread-slots.txt
          95 kB
        3. thread-stacks.txt
          306 kB

          Issue Links

            Activity

              People

              Assignee:
              sue.loverso Susan LoVerso
              Reporter:
              sue.loverso Susan LoVerso
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: