Uploaded image for project: 'Couchbase Go SDK'
  1. Couchbase Go SDK
  2. GOCBC-910

gocbcore.Agent with WaitUntilReady(..) continuously logs in case source doesn't exist

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Not a Bug
    • None
    • None
    • None
    • 1

    Description

      When I try to set up a gocbcore.Agent and use a WaitUntilReady(..) with 10s against a source that doesn't exist, the WaitUntilReady(..) responds back in 10s with the timeout as expected. 

      However, gocbcore seems to continuously be attempting to connect behind the scenes even after WaitUntilReady(..) has responded to the caller.

      I see several logs coming in from GOCBCORE indicating this ..

      2020-06-01T13:36:13.758-07:00 [WARN] (GOCBCORE) Config block decode failure (invalid character 'R' looking for beginning of value) -- cbgt.GocbcoreLogger.Log() at gocbcore_helper.go:615
      2020-06-01T13:36:23.763-07:00 [WARN] (GOCBCORE) Config block decode failure (invalid character 'R' looking for beginning of value) -- cbgt.GocbcoreLogger.Log() at gocbcore_helper.go:615
      2020-06-01T13:36:33.772-07:00 [WARN] (GOCBCORE) Config block decode failure (invalid character 'R' looking for beginning of value) -- cbgt.GocbcoreLogger.Log() at gocbcore_helper.go:615
      ...

      Note that the message `invalid character 'R" looking for beginning of value)` is a json marshaling error of the response returned from ns_server in the event that a source doesn't exist (non-json text) -> "Requested resource not found".

      Attachments

        Issue Links

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

          Activity

            Hi Abhi Dangeti that's the expected behaviour. The SDK will always keep trying to connect (and fetch the cluster config) until the agent is closed. You'll need to close the agent after WaitUntilReady if you want to stop it from trying to reconnect.

            charles.dixon Charles Dixon added a comment - Hi Abhi Dangeti that's the expected behaviour. The SDK will always keep trying to connect (and fetch the cluster config) until the agent is closed. You'll need to close the agent after WaitUntilReady if you want to stop it from trying to reconnect.

            I'm going to resolve this issue, but please reopen it if you aren't satisfied with the above comment.

            charles.dixon Charles Dixon added a comment - I'm going to resolve this issue, but please reopen it if you aren't satisfied with the above comment.
            abhinav Abhi Dangeti added a comment -

            Makes sense, thanks Charles Dixon!

            abhinav Abhi Dangeti added a comment - Makes sense, thanks Charles Dixon !
            abhinav Abhi Dangeti added a comment - http://review.couchbase.org/c/cbgt/+/129619

            People

              charles.dixon Charles Dixon
              abhinav Abhi Dangeti
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty