Uploaded image for project: 'Couchbase node.js Client Library'
  1. Couchbase node.js Client Library
  2. JSCBC-706

Client does not attempt to reconnect on bucket connect errors

    XMLWordPrintable

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 3.0.0, 3.0.1
    • 3.2.5
    • lcb, library
    • None
    • 1
    • SDK 44: Txns, SDK 3.1, Docs

    Description

      Attempting to open a bucket which does not exist causes the SDK to fail to connect and operations are cancelled with 'cluster object was closed' as opposed to continuing to retry the connection and then timing out the operation if it fails to connect in time.

      Attachments

        Issue Links

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

          Activity

            brett19 Brett Lawson added a comment -

            This needs actual testing, but should work now that libcouchbase has resolved the retry behaviour.

            brett19 Brett Lawson added a comment - This needs actual testing, but should work now that libcouchbase has resolved the retry behaviour.
            brett19 Brett Lawson added a comment -

            Unfortunately it does not appear that the libcouchbase behaviour has actually been fully resolved at this point, which causes the Node.js SDK to be unable to support this behaviour.

            brett19 Brett Lawson added a comment - Unfortunately it does not appear that the libcouchbase behaviour has actually been fully resolved at this point, which causes the Node.js SDK to be unable to support this behaviour.

            Linked CCBC-1384 which covers the necessary remaining piece from libcouchbase.

            brett19 Brett Lawson added a comment - Linked CCBC-1384 which covers the necessary remaining piece from libcouchbase.
            pedrodias Pedro Dias added a comment - Is someone looking to implement KVConnectTimeout not being in use? https://forums.couchbase.com/t/nodejs-sdk-3-1-1-kvconnecttimeout-is-not-being-passed-in-options-object-from-cluster-to-connection/30018
            ritam.sharma Ritam Sharma added a comment -

            Brett Lawson - https://issues.couchbase.com/browse/CCBC-1384 is fixed with 3.0.2, is there are date when it will be consumed for nodejs library.

            ritam.sharma Ritam Sharma added a comment - Brett Lawson - https://issues.couchbase.com/browse/CCBC-1384 is fixed with 3.0.2, is there are date when it will be consumed for nodejs library.

            CCBC-1288 causes the behaviour here to be incorrect and we are deferring this out to 3.2.1.

            brett19 Brett Lawson added a comment - CCBC-1288 causes the behaviour here to be incorrect and we are deferring this out to 3.2.1.
            Amereii Asghar Amereii added a comment - - edited

            Brett Lawson I have to use the following code, to get rid of the bug

             

             

            if (
              e.message === 'parent cluster object has been closed'
              ||
              e instanceof Couchbase.ConnectionClosedError
              ||
              e instanceof Couchbase.TimeoutError
            ) 
            {createNewCouchbaseCluster();}
            

             

             

             

            I have 2 cases that the bug occurs in  v3.2.3 

             

            When I reboot the machine that host my NodeJS application (Not the couchbase server, the couchbase server is on another machin), As my NodeJs application is in startup, after rebooting I have `Couchbase.TimeoutError` for any operation immediately, without real timeout, After running `createNewCouchbaseCluster()` that recreated the cluster object, eberything is ok, and If I restart nodejs application everything is ok too

             

            The second case is, When the app runs after days without network issue

            Amereii Asghar Amereii added a comment - - edited Brett Lawson  I have to use the following code, to get rid of the bug     if ( e.message === 'parent cluster object has been closed' || e instanceof Couchbase.ConnectionClosedError || e instanceof Couchbase.TimeoutError ) {createNewCouchbaseCluster();}       I have 2 cases that the bug occurs in  v3.2.3    When I reboot the machine that host my NodeJS application (Not the couchbase server, the couchbase server is on another machin), As my NodeJs application is in startup, after rebooting I have `Couchbase.TimeoutError` for any operation immediately, without real timeout, After running `createNewCouchbaseCluster()` that recreated the cluster object, eberything is ok, and If I restart nodejs application everything is ok too   The second case is, When the app runs after days without network issue

            People

              brett19 Brett Lawson
              brett19 Brett Lawson
              Votes:
              2 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty