Uploaded image for project: 'Couchbase Kafka Connector'
  1. Couchbase Kafka Connector
  2. KAFKAC-167

Sink: Cannot connect to Couchbase on custom port

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 4.0.0-dp.1
    • None
    • 1

    Description

      Attempting to connect using a custom port with the Sink connector results in an error.

      Example config snippet:

       

      connection.cluster_address=192.168.64.4:30711

       

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. KAFKAC-165 Source: Cannot connect to Couchbase on custom port

          • Major - Major loss of function.
          • Resolved
          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            Ascending order - Click to sort in descending order
            david.nault David Nault added a comment -

            Bootstrapping the Couchbase connection with custom ports is supported by SDK 3, but not by the latest SDK 2 (2.7.13) which is what the Kafka connector uses.

            We'll either need to backport the custom port support to SDK 2, or update the DCP client and Kafka connector to use SDK 3.

            david.nault David Nault added a comment - Bootstrapping the Couchbase connection with custom ports is supported by SDK 3, but not by the latest SDK 2 (2.7.13) which is what the Kafka connector uses. We'll either need to backport the custom port support to SDK 2, or update the DCP client and Kafka connector to use SDK 3.
            arun.vijayraghavan Arun Vijayraghavan (Inactive) added a comment -

            Reviving older tickets, I understand the comment on using SDK3 or backporting the fix to SDK2 

            How were we able to fix https://issues.couchbase.com/browse/KAFKAC-165.  looks like the same problem but with Source Connector ?

            arun.vijayraghavan Arun Vijayraghavan (Inactive) added a comment - Reviving older tickets, I understand the comment on using SDK3 or backporting the fix to SDK2  How were we able to fix  https://issues.couchbase.com/browse/KAFKAC-165 .  looks like the same problem but with Source Connector ?
            david.nault David Nault added a comment -

            Arun Vijayraghavan The Source connector is driven by the Java DCP client, which does support bootstrapping via custom ports. 

            david.nault David Nault added a comment - Arun Vijayraghavan  The Source connector is driven by the Java DCP client, which does support bootstrapping via custom ports. 
            david.nault David Nault added a comment -

            Resolved in 4.0.0-pre.1 which uses SDK 3

            david.nault David Nault added a comment - Resolved in 4.0.0-pre.1 which uses SDK 3

            People

              david.nault David Nault
              david.nault David Nault
              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