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

"seqno_acknowledge failed because this vbucket doesn't exist" disconnects replication

    XMLWordPrintable

Details

    • Untriaged
    • 1
    • No

    Description

      If the timing of a "seqno-ack" from consumer to producer is just right, it can find that the active vbucket has been deleted, the producer will respond to the consumer with "not-my-vbucket". The consumer will receive the response packet and error as follows:

      WARNING 121: Unsupported response packet received with opcode: 0x61 (DCP_SEQNO_ACKNOWLEDGED)
      

      The error happens because "mcbp" has no response handler configured for this opcode. This forces a disconnect of replication, which will fail a rebalance.

      Clearly from the code, a seqno-ack can generate a response and we should gracefully handle them to avoid unexpected disconnects and rebalance failure.

      Attachments

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

        Activity

          There are no commits yet on this issue.

          People

            jwalker Jim Walker
            jwalker Jim Walker
            Votes:
            1 Vote for this issue
            Watchers:
            12 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty