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

Disable truncate testing with LSM

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.6.4, 3.7.3, WT3.1.0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None

      Configuring even a single WT_SESSION.truncate operation in format causes a test timeout (which means the operation is taking at least 15 minutes, the default format timeout value).

      A sample CONFIG:

      ############################################
      #  RUN PARAMETERS
      ############################################
      abort=0
      alter=0
      auto_throttle=1
      backups=0
      bitcnt=3
      bloom=1
      bloom_bit_count=15
      bloom_hash_count=17
      bloom_oldest=0
      cache=300
      cache_minimum=20
      checkpoints=wiredtiger
      checkpoint_log_size=62
      checkpoint_wait=85
      checksum=on
      chunk_size=10
      compaction=0
      compression=snappy
      data_extend=0
      data_source=lsm
      delete_pct=13
      dictionary=0
      direct_io=0
      encryption=rotn-7
      evict_max=3
      file_type=row-store
      firstfit=0
      huffman_key=0
      huffman_value=0
      independent_thread_rng=1
      in_memory=0
      insert_pct=61
      internal_key_truncation=1
      internal_page_max=9
      isolation=random
      key_gap=14
      key_max=256
      key_min=256
      leaf_page_max=9
      leak_memory=0
      logging=1
      logging_archive=0
      logging_compression=lz4-noraw
      logging_file_max=146059
      logging_prealloc=0
      long_running_txn=0
      lsm_worker_threads=4
      merge_max=17
      mmap=1
      modify_pct=19
      ops=100000
      prefix_compression=0
      prefix_compression_min=0
      quiet=1
      read_pct=2
      rebalance=1
      repeat_data_pct=58
      reverse=0
      rows=100000
      runs=1
      salvage=1
      split_pct=90
      statistics=0
      statistics_server=1
      threads=1
      timer=4
      transaction_timestamps=0
      transaction-frequency=49
      truncate=1
      value_max=2108
      value_min=256
      verify=1
      wiredtiger_config=
      write_pct=5
      ############################################
      

      And here's the single-thread stack after the timeout:

      (gdb) where
      #0  0x000000000057b356 in __wt_buf_set (session=0x7f96245f4210, 
          buf=0x7f96041c97d0, data=0x7f96044fdc38, size=256)
          at ./src/include/buf.i:84
      #1  0x000000000057f99d in __cursor_key_order_check_row (
          session=0x7f96245f4210, cbt=0x7f96041c94e0, next=true)
          at src/btree/bt_curnext.c:415
      #2  0x000000000057fb49 in __wt_cursor_key_order_check (session=0x7f96245f4210, 
          cbt=0x7f96041c94e0, next=true) at src/btree/bt_curnext.c:448
      #3  0x000000000058027d in __wt_btcur_next (cbt=0x7f96041c94e0, 
          truncating=false) at src/btree/bt_curnext.c:669
      #4  0x0000000000522f1e in __curfile_next (cursor=0x7f96041c94e0)
          at src/cursor/cur_file.c:96
      #5  0x000000000055d31c in __clsm_next (cursor=0x7f960404bd40)
          at src/lsm/lsm_cursor.c:959
      #6  0x000000000057336e in __wt_range_truncate (start=0x7f960404bd40, 
          stop=0x7f96045af540) at src/schema/schema_truncate.c:121
      #7  0x0000000000573520 in __wt_schema_range_truncate (session=0x7f96245f4210, 
          start=0x7f960404bd40, stop=0x7f96045af540)
          at src/schema/schema_truncate.c:155
      #8  0x000000000048a4f7 in __wt_session_range_truncate (session=0x7f96245f4210, 
          uri=0x0, start=0x7f960404bd40, stop=0x7f96045af540)
          at src/session/session_api.c:1421
      #9  0x000000000048ae26 in __session_truncate (wt_session=0x7f96245f4210, 
          uri=0x0, start=0x7f960404bd40, stop=0x7f96045af540, config=0x0)
          at src/session/session_api.c:1492
      #10 0x000000000040a9af in row_truncate (tinfo=0x4fb0210, cursor=0x7f960404bd40)
          at ops.c:1619
      

            Assignee:
            backlog-server-execution [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            keith.bostic@mongodb.com Keith Bostic (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: