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

Set session max on all configuration strings in timestamp_abort test

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.0.4, 4.1.4, WT3.2.0
    • Component/s: None
    • Labels:
    • Sprint:
      Storage Engines 2018-10-08

      Description

      http://build.wiredtiger.com:8080/job/wiredtiger-test-recovery-stress/52363/console

      + ./test_timestamp_abort -C -m
      Parent: compatibility: true, in-mem log sync: true, timestamp in use: true
      Parent: Create 169 threads; sleep 37 seconds
      CONFIG: test_timestamp_abort -C -m -h WT_TEST.timestamp-abort -T 169 -t 37
      Create checkpoint thread
      Create timestamp thread
      Create 169 writer threads
      Thread 2 starts at 2000000000
      ...
      Thread 103 starts at 103000000000
      Thread 104 starts at 104000000000
      Thread 105 starts at 105000000000
      [1538138763:736196][24011:0x7f655ffff700], WT_CONNECTION.open_session: __open_session, 2161: out of sessions, configured for 134 (including internal sessions): WT_ERROR: non-specific WiredTiger error
      test_timestamp_abort: FAILED: thread_run/286: td->conn->open_session(td->conn, NULL, NULL, &session): WT_ERROR: non-specific WiredTiger error
      process aborting
      test_timestamp_abort: FAILED: thread_run/286: td->conn->open_session(td->conn, NULL, NULL, &session): WT_ERROR: non-specific WiredTiger error
      process aborting
      [1538138763:736259][24011:0x7f65577fe700], WT_CONNECTION.open_session: __open_session, 2161: out of sessions, configured for 134 (including internal sessions): WT_ERROR: non-specific WiredTiger error
      test_timestamp_abort: FAILED: thread_run/303: td->conn->open_session( td->conn, NULL, NULL, &oplog_session): WT_ERROR: non-specific WiredTiger error
      process aborting
      [1538138763:736312][24011:0x7f654e7fc700], WT_CONNECTION.open_session: __open_session, 2161: out of sessions, configured for 134 (including internal sessions): WT_ERROR: non-specific WiredTiger error
      test_timestamp_abort: FAILED: thread_run/286: td->conn->open_session(td->conn, NULL, NULL, &session): WT_ERROR: non-specific WiredTiger error
      process aborting
      [1538138763:736347][24011:0x7f654effd700], WT_CONNECTION.open_session: __open_session, 2161: out of sessions, configured for 134 (including internal sessions): WT_ERROR: non-specific WiredTiger error
      test_timestamp_abort: FAILED: thread_run/286: td->conn->open_session(td->conn, NULL, NULL, &session): WT_ERROR: non-specific WiredTiger error
      process aborting
      [1538138763:736389][24011:0x7f654dffb700], WT_CONNECTION.open_session: __open_session, 2161: out of sessions, configured for 134 (including internal sessions): WT_ERROR: non-specific WiredTiger error
      test_timestamp_abort: FAILED: thread_run/286: td->conn->open_session(td->conn, NULL, NULL, &session): WT_ERROR: non-specific WiredTiger error
      process aborting
      [1538138763:736421][24011:0x7f654d7fa700], WT_CONNECTION.open_session: __open_session, 2161: out of sessions, configured for 134 (including internal sessions): WT_ERROR: non-specific WiredTiger error
      test_timestamp_abort: FAILED: thread_run/286: td->conn->open_session(td->conn, NULL, NULL, &session): WT_ERROR: non-specific WiredTiger error
      process aborting
      [1538138763:736457][24011:0x7f65dafe5700], WT_CONNECTION.open_session: __open_session, 2161: out of sessions, configured for 134 (including internal sessions): WT_ERROR: non-specific WiredTiger error
      test_timestamp_abort: FAILED: thread_run/303: td->conn->open_session( td->conn, NULL, NULL, &oplog_session): WT_ERROR: non-specific WiredTiger error
      process aborting
      Parent: compatibility: true, in-mem log sync: true, timestamp in use: true
      Parent: Create 169 threads; sleep 37 seconds
      CONFIG: test_timestamp_abort -C -m -h WT_TEST.timestamp-abort -T 169 -t 37
      test_timestamp_abort: FAILED: Child process 24011 abnormally exited: Invalid argument
      

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              sue.loverso Susan LoVerso
              Reporter:
              keith.bostic Keith Bostic
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: