Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. MB-19387

[FTS] Forestdb segmentation fault: failed to read B+- Tree block

    XMLWordPrintable

Details

    • Untriaged
    • No
    • ForestDB: Oct 17 - Nov 4

    Description

      Build
      4.5.0-2363

      Testcase
      ./testrunner -i INI_FILE.ini -p get-cbcollect-info=True,get-coredumps=True,get-logs=False,stop-on-failure=False,GROUP=P1 -t fts.stable_topology_fts.StableTopFTS.index_query_in_parallel,items=1000000,num_queries=200,GROUP=P1

      Multiple crashes seen in few mins. Kernel panics on vm and it goes offline. This may not be reproducible again. I've saved breakpad dump file, forestdb file at 172.23.107.187:/root/new_segv/

      In fts.log

      [FDB ERR] Read error: read offset 492866064413323264 exceeds the file's current offset 676913152 in a database file '/opt/couchbase/var/lib/couchbase/data/@fts/default_index_b8d513879b504b53_cd5a61e8.pindex/store.0'
       
      [FDB ERR] Failed to read the B+-Tree block (block id: 120328629007159, block address: 0x7f4eba047000)
      Caught SIGSEGV in libforestdb at (null)
      Breakpad caught a crash in forestdb. Writing crash dump to ./41c96036-be6c-0896-7bdad671-68f166db.dmp before terminating.
      

      GDBing breakpad generated core:

      (gdb) bt
      #0  _fetch_bnode (btree=0x7f4f6f3bda90, key=Cannot access memory at address 0x7f4f6f3bc950
      ) at /home/couchbase/jenkins/workspace/watson-unix/forestdb/src/btree.cc:50
      #1  btree_find (btree=0x7f4f6f3bda90, key=Cannot access memory at address 0x7f4f6f3bc950
      ) at /home/couchbase/jenkins/workspace/watson-unix/forestdb/src/btree.cc:688
      Cannot access memory at address 0x7f4f6f3bc998
      

      Attachments

        Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              apiravi Aruna Piravi (Inactive)
              apiravi Aruna Piravi (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty