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

Increase startup timeout to 30 seconds for slow I/O systems

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.6.9, 4.0.3, 4.1.3, WT3.2.0
    • Affects Version/s: None
    • Component/s: None
    • Storage Engines 2018-09-10

      There was a failure in automated testing:

      CONFIG: test_schema_abort -m -h WT_TEST.schema-abort -T 5 -t 10
      Create checkpoint thread
      Create timestamp thread
      Create 5 writer threads
      After 10 seconds stable still not set. Aborting.
      THREAD 0: ts: 33747
      THREAD 1: ts: 33746
      THREAD 2: ts: 4
      THREAD 3: ts: 3
      THREAD 4: ts: 11
      Thread 1 starts at 1000000000
      Thread 3 starts at 3000000000
      Thread 2 starts at 2000000000
      Thread 0 starts at 0
      Thread 4 starts at 4000000000
      CKPT: !stable_set time 1
      CKPT: !stable_set time 1
      CKPT: !stable_set time 1
      CKPT: !stable_set time 2
      CKPT: !stable_set time 3
      CKPT: !stable_set time 3
      CKPT: !stable_set time 3
      CKPT: !stable_set time 3
      CKPT: !stable_set time 4
      CKPT: !stable_set time 5
      CKPT: !stable_set time 6
      CKPT: !stable_set time 6
      CKPT: !stable_set time 7
      CKPT: !stable_set time 7
      CKPT: !stable_set time 7
      CKPT: !stable_set time 8
      CKPT: !stable_set time 8
      CKPT: !stable_set time 9
      CKPT: !stable_set time 10
      CKPT: !stable_set time 11
      Parent: compatibility: false, in-mem log sync: true, timestamp in use: true
      Parent: Create 5 threads; sleep 10 seconds
      CONFIG: test_schema_abort -m -h WT_TEST.schema-abort -T 5 -t 10
      test_schema_abort: FAILED: Child process 13611 abnormally exited: Invalid argument
      process aborting
      ../../../test/csuite/schema_abort/smoke.sh: line 8: 13573 Aborted                 (core dumped) $TEST_WRAPPER ./test_schema_abort -m -t 10 -T 5
      FAIL schema_abort/smoke.sh (exit status: 134)
      

      This has a similar signature to WT-4210, but the change was committed for that ticket. The core dump showed:

      Core was generated by `./test_schema_abort -m -t 10 -T 5'.
      Program terminated with signal SIGABRT, Aborted.
      #0  0x00007f078b672428 in __GI_raise (sig=sig@entry=6)
          at ../sysdeps/unix/sysv/linux/raise.c:54
      54	../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
      (gdb) where
      #0  0x00007f078b672428 in __GI_raise (sig=sig@entry=6)
          at ../sysdeps/unix/sysv/linux/raise.c:54
      #1  0x00007f078b67402a in __GI_abort () at abort.c:89
      #2  0x00000000004057db in testutil_die (e=22, 
          fmt=0x406e88 "Child process %lu abnormally exited")
          at ../../../test/utility/misc.c:62
      #3  0x000000000040429d in sig_handler (sig=17)
          at ../../../test/csuite/schema_abort/main.c:946
      #4  <signal handler called>
      #5  0x00007f078b7092f0 in __nanosleep_nocancel ()
          at ../sysdeps/unix/syscall-template.S:84
      #6  0x00007f078b70925a in __sleep (seconds=0) at ../sysdeps/posix/sleep.c:55
      #7  0x00000000004046f4 in main (argc=0, argv=0x7ffeee75a558)
          at ../../../test/csuite/schema_abort/main.c:1091
      

      Which I believe is expected. The original failure can be seen here:
      http://build.wiredtiger.com:8080/job/wiredtiger/6811/console

            Assignee:
            sue.loverso@mongodb.com Susan LoVerso
            Reporter:
            alexander.gorrod@mongodb.com Alexander Gorrod
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: