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

SDK currently ignores the networkType value specified by the user

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.5.1
    • Fix Version/s: 1.5.2
    • Component/s: library
    • Labels:
      None

      Description

      The SDK currently appares to ignore the value specified by the user and instead uses the heuristic in all cases.  This is an error and the heuristic should only be used if there is no value specified, or the value is 'auto'.

        Attachments

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

          Activity

          Hide
          charles.dixon Charles Dixon added a comment -

          When the client processes a new configuration from the server, it should log a listing of each node which was found within the configuration (at DEBUG level). For each node, the SDK should log both the default hostname/port information as well as the hostname/port information for the alternate name the client is configured to be using. In the case that the SDK is configured to use the default hostname/port’s, it should only log the information once.

          During bootstrap, the SDK must log (at INFO level) which network it is intending to use for its connections. This will either be the value selected by the ‘network’ connection string option, or the value selected by the network selection heuristic described above.
          Errors and Error Handling

          We don't appear to log this info either.

          Show
          charles.dixon Charles Dixon added a comment - When the client processes a new configuration from the server, it should log a listing of each node which was found within the configuration (at DEBUG level). For each node, the SDK should log both the default hostname/port information as well as the hostname/port information for the alternate name the client is configured to be using. In the case that the SDK is configured to use the default hostname/port’s, it should only log the information once. During bootstrap, the SDK must log (at INFO level) which network it is intending to use for its connections. This will either be the value selected by the ‘network’ connection string option, or the value selected by the network selection heuristic described above. Errors and Error Handling We don't appear to log this info either.
          Hide
          build-team Couchbase Build Team added a comment -

          Build couchbase-server-6.5.0-2065 contains gocbcore commit 76005f5 with commit message:
          GOCBC-380: Fix initial route config to not ignore networkType

          Show
          build-team Couchbase Build Team added a comment - Build couchbase-server-6.5.0-2065 contains gocbcore commit 76005f5 with commit message: GOCBC-380 : Fix initial route config to not ignore networkType
          Hide
          build-team Couchbase Build Team added a comment -

          Build sync_gateway-2.6.0-2 contains gocbcore commit 76005f5 with commit message:
          GOCBC-380: Fix initial route config to not ignore networkType

          Show
          build-team Couchbase Build Team added a comment - Build sync_gateway-2.6.0-2 contains gocbcore commit 76005f5 with commit message: GOCBC-380 : Fix initial route config to not ignore networkType
          Hide
          build-team Couchbase Build Team added a comment -

          Build sync_gateway-2.5.1-8 contains gocbcore commit 76005f5 with commit message:
          GOCBC-380: Fix initial route config to not ignore networkType

          Show
          build-team Couchbase Build Team added a comment - Build sync_gateway-2.5.1-8 contains gocbcore commit 76005f5 with commit message: GOCBC-380 : Fix initial route config to not ignore networkType

            People

            • Assignee:
              charles.dixon Charles Dixon
              Reporter:
              brett19 Brett Lawson
            • 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

                  Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.