Uploaded image for project: 'Couchbase C client library libcouchbase'
  1. Couchbase C client library libcouchbase
  2. CCBC-627

Poll regularly for config updates

    XMLWordPrintable

Details

    • Task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 2.5.1
    • 2.7.5
    • None
    • Security Level: Public
    • build 3508 running cbc-n1qlback

    Description

      start a cluster with 2 query nodes
      start cbc-n1qlback with some query
      add a new query node to the cluster and rebalance
      observe the request/sec per node

      expected: topology changes should eb automatically picked up by the clients. after rebalance the new query node needs to be part of the round robin requests being sent to the cluster. however new node does not start taking traffic even after a long wait.

      if the load is stopped and restarted, the requests do go to the newly added node as well. However this means topology changes would require a restart of the app servers. that does cause admin overhead and possibly failed requests for the app and downtime.

      Attachments

        Issue Links

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

          Activity

            cihan Cihan Biyikoglu (Inactive) created issue -
            cihan Cihan Biyikoglu (Inactive) made changes -
            Field Original Value New Value
            Description start a cluster with 2 query nodes
            start cbc-n1qlback with some query
            add a new query node to the cluster and rebalance
            observe the request/sec per node

            expected: after rebalance the new query node needs to be part of the round robin requests being sent to the cluster. however new node does not start taking traffic even after a long wait.

            if the load is stopped and restarted, the requests do go to the newly added node as well. However this means adding a new node would require a restart of the app servers.
            start a cluster with 2 query nodes
            start cbc-n1qlback with some query
            add a new query node to the cluster and rebalance
            observe the request/sec per node

            expected: after rebalance the new query node needs to be part of the round robin requests being sent to the cluster. however new node does not start taking traffic even after a long wait.

            if the load is stopped and restarted, the requests do go to the newly added node as well. However this means topology changes would require a restart of the app servers. that does cause admin overhead and possibly failed requests for the app and downtime.
            cihan Cihan Biyikoglu (Inactive) made changes -
            Description start a cluster with 2 query nodes
            start cbc-n1qlback with some query
            add a new query node to the cluster and rebalance
            observe the request/sec per node

            expected: after rebalance the new query node needs to be part of the round robin requests being sent to the cluster. however new node does not start taking traffic even after a long wait.

            if the load is stopped and restarted, the requests do go to the newly added node as well. However this means topology changes would require a restart of the app servers. that does cause admin overhead and possibly failed requests for the app and downtime.
            start a cluster with 2 query nodes
            start cbc-n1qlback with some query
            add a new query node to the cluster and rebalance
            observe the request/sec per node

            expected: topology changes should eb automatically picked up by the clients. after rebalance the new query node needs to be part of the round robin requests being sent to the cluster. however new node does not start taking traffic even after a long wait.

            if the load is stopped and restarted, the requests do go to the newly added node as well. However this means topology changes would require a restart of the app servers. that does cause admin overhead and possibly failed requests for the app and downtime.
            mnunberg Mark Nunberg (Inactive) made changes -
            Status New [ 10003 ] Resolved [ 5 ]
            mnunberg Mark Nunberg (Inactive) made changes -
            Status Resolved [ 5 ] Reopened [ 4 ]
            mnunberg Mark Nunberg (Inactive) made changes -
            Fix Version/s 2.5.1 [ 12808 ]
            mnunberg Mark Nunberg (Inactive) made changes -
            Summary clients don't utilize a newly added node to the cluster Poll regularly for config updates
            mnunberg Mark Nunberg (Inactive) made changes -
            Fix Version/s .future [ 11337 ]
            mnunberg Mark Nunberg (Inactive) made changes -
            Fix Version/s 2.7.5 [ 14404 ]
            Fix Version/s .future [ 11337 ]
            mnunberg Mark Nunberg (Inactive) made changes -
            Labels n1ql fast_failover n1ql
            mnunberg Mark Nunberg (Inactive) made changes -
            Status Reopened [ 4 ] In Progress [ 3 ]
            mnunberg Mark Nunberg (Inactive) made changes -
            Link This issue relates to CCBC-760 [ CCBC-760 ]
            mnunberg Mark Nunberg (Inactive) made changes -
            Resolution Fixed [ 1 ]
            Status In Progress [ 3 ] Resolved [ 5 ]

            People

              mnunberg Mark Nunberg (Inactive)
              cihan Cihan Biyikoglu (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty