Uploaded image for project: 'Couchbase Gateway'
  1. Couchbase Gateway
  2. CBG-3834

Force disconnection of blip clients on database close

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Unresolved
    • Major
    • Boron
    • None
    • SyncGateway
    • Security Level: Public
    • None
    • 8

    Description

      On database close Sync Gateway will close the underlying database connection, but doesn't automatically close BlipSyncContexts using that database.  Any subsequent requests made by clients using that connection that attempt to use the database will receive a 500 error like:

      2024-02-28T16:13:01.477-08:00 [WRN] c:[6eb873e7] db:mydb CheckProposedRev("docid") --> *errors.withStack SubdocGetBodyAndXattr <ud>username</ud>: connection shut down -- db.(*DatabaseCollection).CheckProposedRev() at crud.go:2530

      This relies on clients to disconnect and reconnect in response to the 500 error.  It would be preferable for SGW to explicitly close the BlipSyncContext.

      Attachments

        Issue Links

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

          Activity

            People

              The One The One
              adamf Adam Fraser
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty