Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. MB-40596

[CX] analytics dcp client does not support remote links to alternate addresses

    XMLWordPrintable

    Details

    • Triage:
      Untriaged
    • Story Points:
      1
    • Is this a Regression?:
      Unknown
    • Sprint:
      CX Sprint 209

      Description

      The analytics DCP client does not currently have support for alternate addresses- all connections are made on main hostname only.

      There is no workaround, other than to not use remote clusters configured w/ alternate addresses.

        Attachments

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

          Activity

          michael.blow Michael Blow created issue -
          michael.blow Michael Blow made changes -
          Field Original Value New Value
          Status Open [ 1 ] In Progress [ 3 ]
          till Till Westmann made changes -
          Due Date 23/Jul/20
          till Till Westmann made changes -
          Labels needs-functional-test needs-functional-test triaged
          till Till Westmann made changes -
          Link This issue blocks MB-38724 [ MB-38724 ]
          till Till Westmann made changes -
          Labels needs-functional-test triaged approved-for-6.6.0 needs-functional-test triaged
          michael.blow Michael Blow made changes -
          Resolution Fixed [ 1 ]
          Status In Progress [ 3 ] Resolved [ 5 ]
          umang.agrawal Umang made changes -
          VERIFICATION STEPS Below scenarios tests the functionality of alternate address when default address is unresolvable.
          Scenario 1 - setting up ip address as alternate name:

          1. setup 2 cluster with hostnames. 1 local analytics cluster and 1 remote data cluster.
          2. create alternate address for remote cluster as
          ./couchbase-cli setting-alternate-address --cluster secu01.qe.couchbase.com:8091 -u Administrator -p password --set --node secu01.qe.couchbase.com --hostname 172.23.97.52
          3. create link to remote cluster on local cluster using the alternate address set in step 2.
          4. get link info and check for bootstrapAlternateAddress=true
          5. create dataset using the above link in local cluster.
          6. connect link.
          7. remove the above hostname entry from /etc/hosts file on local cluster VM.
          8. disconnect link and connect back.
          9. data is ingested succesfully.

          Scenario 2 - setting up hostname as alternate name:

          1. setup 2 cluster with hostnames. 1 local analytics cluster and 1 remote data cluster.
          2. create alternate address for remote cluster as
          ./couchbase-cli setting-alternate-address --cluster 172.23.97.52:8091 -u Administrator -p password --set --node 172.23.97.52 --hostname secu01.qe.couchbase.com
          3. create link to remote cluster on local cluster using the alternate address set in step 2.
          4. get link info and check for bootstrapAlternateAddress=true
          5. create dataset using the above link in local cluster.
          6. connect link.
          7. data ingestion is successful
          8. remove the above hostname entry from /etc/hosts file on local cluster VM.
          9. disconnect link and connect back.
          10. link connection fails as expected.

          Scenario 1 and 2 were tested with following combination of ip address families.
          1. Both local and remote cluster in Ipv4 mode - alternate address works
          2. analytics in IPv4 and remote in IPv6 - checked with hostname and ip address didn’t work. (able to ping IPv6 VM from IPv4 using ping6)
          3. analytics in IPv6 and remote in Ipv4 - works with both hostname, ip address and alternate address
          4. Both local and remote cluster in Ipv6 mode - alternate address works

          Below scenario tests the functionality of alternate address when default address in unreachable. Only tested with cluster configured with IPv4 family.

          Scenario 1 (suggested by Thuan Nguyen):
          1. setup cluster with internal IP address on AWS EC2 instance.
          2. create a default bucket
          3. then from local system, use cbworkloadgen to load data to default bucket
          4. It will fail to load data, since node is not reachable.
          5. after setting external IP of AWS EC2 instance as Alternate Address for the node in cluster, cbworkloadgen is able to load data to cluster.

          Scenario 2 -
          1. Setup a local cluster with analytics node.
          2. Setup a remote cluster on AWS EC2 with data node with private aws ip.
          3. try creating link from local cluster to remote cluster. It fails.
          4. set alternate address on remote cluster node on AWS to EC2 instances public IP.
          5. create link using this alternate address.
          6. list link to check whether it is bootstrapping from alternate address or not.
          7. create dataset on the link.
          8. connect link and check for data ingestion.
          9. data ingestion is successfull.
          10. disconnect link.
          11. add some documents in remote cluster bucket on which dataset was created.
          12. reconnect the link.
          13. new documents are also ingested successfully
          Assignee Michael Blow [ michael.blow ] Umang [ JIRAUSER24787 ]
          Status Resolved [ 5 ] Closed [ 6 ]

            People

            Assignee:
            umang.agrawal Umang
            Reporter:
            michael.blow Michael Blow
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Due:
              Created:
              Updated:
              Resolved:

                Gerrit Reviews

                There is 1 open Gerrit change

                  PagerDuty