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

Unlock when sleeping to allow other log threads to make progress

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

      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
      

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

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

              Created:
              Updated:
              Resolved: