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

session naming core dump

    • Type: Icon: Task Task
    • Resolution: Done
    • WT1.2
    • Affects Version/s: None
    • Component/s: None

      I just triggered this core dump on bengal, I'm putting it into a separate issue because I don't think it's related to what I'm looking for – it looks to me like this might be a race in the session naming layer?

         2: read/write ops: search 0, insert 522, update 858, remove 93
      Program received signal SIGSEGV, Segmentation fault.
      [Switching to Thread 0x7fffeebfd700 (LWP 2964)]
      0x0000000000416b3a in __wt_session_get_btree (session=0x7e1f80, uri=0x5934d3 "file:__wt", cfg=0x7fffeebfcd20, flags=128)
          at ../src/session/session_btree.c:150
      150			if (strcmp(uri, btree->name) != 0)
      Missing separate debuginfos, use: debuginfo-install bzip2-libs-1.0.5-7.el6_0.x86_64 glibc-2.12-1.47.el6_2.5.x86_64
      (gdb) where
      #0  0x0000000000416b3a in __wt_session_get_btree (session=0x7e1f80, uri=0x5934d3 "file:__wt", cfg=0x7fffeebfcd20, flags=128)
          at ../src/session/session_btree.c:150
      WT-1  0x00000000004480e9 in __wt_schema_worker (session=0x7e1f80, uri=0x5934d3 "file:__wt", cfg=0x7fffeebfcd20, 
          func=0x417080 <__wt_snapshot>, open_flags=128) at ../src/schema/schema_worker.c:29
      WT-2  0x00000000004159c1 in __session_sync (wt_session=0x7e1f80, uri=0x5934d3 "file:__wt", config=0x7fffeebfcda0 "snapshot=thread-9")
          at ../src/session/session_api.c:281
      WT-3  0x0000000000406f08 in ops (arg=0x7e8630) at ../../../test/format/wts_ops.c:174
      WT-4  0x00000030f38077f1 in start_thread () from /lib64/libpthread.so.0
      WT-5  0x00000030f34e592d in clone () from /lib64/libc.so.6
      (gdb) p btree
      $1 = (WT_BTREE *) 0x4f3000004f3
      (gdb) p uri
      $2 = 0x5934d3 "file:__wt"
      (gdb) p btree->name
      Cannot access memory at address 0x4f30000051b
      (gdb) where
      #0  0x0000000000416b3a in __wt_session_get_btree (session=0x7e1f80, uri=0x5934d3 "file:__wt", cfg=0x7fffeebfcd20, flags=128)
          at ../src/session/session_btree.c:150
      WT-1  0x00000000004480e9 in __wt_schema_worker (session=0x7e1f80, uri=0x5934d3 "file:__wt", cfg=0x7fffeebfcd20, 
          func=0x417080 <__wt_snapshot>, open_flags=128) at ../src/schema/schema_worker.c:29
      WT-2  0x00000000004159c1 in __session_sync (wt_session=0x7e1f80, uri=0x5934d3 "file:__wt", config=0x7fffeebfcda0 "snapshot=thread-9")
          at ../src/session/session_api.c:281
      WT-3  0x0000000000406f08 in ops (arg=0x7e8630) at ../../../test/format/wts_ops.c:174
      WT-4  0x00000030f38077f1 in start_thread () from /lib64/libpthread.so.0
      WT-5  0x00000030f34e592d in clone () from /lib64/libc.so.6
      

      The config is pretty hellish, I stumbled across it while trying to make my error trigger.

      bzip=0
      cache=1
      delete_pct=7
      file_type=row-store
      huffman_key=0
      huffman_value=0
      insert_pct=35
      internal_page_max=9
      key_max=120
      key_min=12
      leaf_page_max=9
      ops=4000
      # repeat_data_pct not applicable to this run
      reverse=0
      rows=1000
      runs=0
      threads=25
      value_max=1448
      value_min=20  
      write_pct=66
      

            Assignee:
            Unassigned Unassigned
            Reporter:
            keith.bostic@mongodb.com Keith Bostic (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: