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

exception occurred in runloop - closing connection: bad_function_call

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Major
    • 5.5.0
    • None
    • memcached
    • None
    • Untriaged
    • Unknown

    Description

      Seen in MB-28626 but not yet identified as the cause of the Checkpoint::queueDirty issue seen in MB-28626

      Seeing the following error only in cbcollect_info_ns_1@172.23.108.103_20180311-204413/memcached.log

      2018-03-11T10:49:17.590337Z WARNING 64: exception occurred in runloop - closing connection: bad_function_call
      		 
       
      		 
      > grep bad_func memcached.log | wc -l
      		 
        115829

      The error stops occurring at 2018-03-11T10:49:19 and the first queueDirty error occurs 30 minutes later (the queueDirty error happens on a different node but .103 holds the active VB for the first VB which reported the queueDirty issue)

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. MB-28626 memcached exits with status 134 and rebalance failures in centos longevity

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. MB-28733 ASan: heap-use-after-free in notify_io_complete

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed
          For Gerrit Dashboard: MB-28630
          # Subject Branch Project Status CR V
          90843,2 MB-28630: Extend log info for exception in runloop master kv_engine Status: MERGED +2 +1
          90844,5 MB-28630: Try to catch std::bad_function_call during privilege check master kv_engine Status: MERGED +2 +1

          Activity

            People

              trond Trond Norbye
              jwalker Jim Walker
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty