Uploaded image for project: 'Couchbase .NET client library'
  1. Couchbase .NET client library
  2. NCBC-962

Queries are not successful after rebalance swap of a query node

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.1.4
    • Component/s: None
    • Labels:
      None
    • Environment:
      2.1.3

      Description

      Cluster with 1 data, 1 query and 2 index nodes. After swap rebalance of the query node with another query node, query ops are not successful.
      The updated config map is received but the sdk always sends the request to the rebalanced out node.

        Attachments

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

          Activity

          Hide
          jmorris Jeff Morris added a comment -

          I see a lot of this:

          Line 9861: 2015-07-29 16:59:01,816 [14] ERROR Couchbase.N1QL.QueryClient - System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 172.23.105.232:8093
          Line 9863: at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
          Line 9870: 2015-07-29 16:59:01,880 [9] ERROR SaslFactory - System.Net.Sockets.SocketException (0x80004005): The requested address is not valid in its context

          Show
          jmorris Jeff Morris added a comment - I see a lot of this: Line 9861: 2015-07-29 16:59:01,816 [14] ERROR Couchbase.N1QL.QueryClient - System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 172.23.105.232:8093 Line 9863: at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception) Line 9870: 2015-07-29 16:59:01,880 [9] ERROR SaslFactory - System.Net.Sockets.SocketException (0x80004005): The requested address is not valid in its context
          Hide
          jmorris Jeff Morris added a comment -

          And this:

          2015-07-29 16:56:51,509 [4] INFO Couchbase.IO.ConnectionPool`1[[Couchbase.IO.Connection, Couchbase.NetClient, Version=2.0.0.0, Culture=neutral, PublicKeyToken=null]] - System.Net.Sockets.SocketException (0x80004005): The requested address is not valid in its context
          at System.Net.Sockets.Socket.DoBeginConnect(EndPoint endPointSnapshot, SocketAddress socketAddress, LazyAsyncResult asyncResult)
          at System.Net.Sockets.Socket.BeginConnect(EndPoint remoteEP, AsyncCallback callback, Object state)
          at Couchbase.IO.DefaultConnectionFactory.<GetGeneric>b__0[T](IConnectionPool`1 p, IByteConverter c, BufferAllocator b) in c:\couchbase-net-client\Src\Couchbase\IO\DefaultConnectionFactory.cs:line 25
          at Couchbase.IO.ConnectionPool`1.Initialize() in c:\couchbase-net-client\Src\Couchbase\IO\ConnectionPool.cs:line 112

          Show
          jmorris Jeff Morris added a comment - And this: 2015-07-29 16:56:51,509 [4] INFO Couchbase.IO.ConnectionPool`1[ [Couchbase.IO.Connection, Couchbase.NetClient, Version=2.0.0.0, Culture=neutral, PublicKeyToken=null] ] - System.Net.Sockets.SocketException (0x80004005): The requested address is not valid in its context at System.Net.Sockets.Socket.DoBeginConnect(EndPoint endPointSnapshot, SocketAddress socketAddress, LazyAsyncResult asyncResult) at System.Net.Sockets.Socket.BeginConnect(EndPoint remoteEP, AsyncCallback callback, Object state) at Couchbase.IO.DefaultConnectionFactory.<GetGeneric>b__0 [T] (IConnectionPool`1 p, IByteConverter c, BufferAllocator b) in c:\couchbase-net-client\Src\Couchbase\IO\DefaultConnectionFactory.cs:line 25 at Couchbase.IO.ConnectionPool`1.Initialize() in c:\couchbase-net-client\Src\Couchbase\IO\ConnectionPool.cs:line 112
          Hide
          subhashni Subhashni Balakrishnan (Inactive) added a comment -

          yes 172.23.105.232 was rebalanced out. This was the latest config

          nodesExt":[{"services":

          {"mgmt":8091,"moxi":11211,"kv":11210,"capi":8092,"kvSSL":11207,"capiSSL":18092,"mgmtSSL":18091,"projector":9999,"indexAdmin":0,"indexScan":0,"indexHttp":0,"indexStreamInit":0,"indexStreamCatchup":0,"indexStreamMaint":0,"n1ql":0}

          ,"hostname":"172.23.105.230"},{"services":

          {"mgmt":8091,"moxi":0,"kv":0,"capi":0,"kvSSL":0,"capiSSL":0,"mgmtSSL":18091,"projector":0,"indexAdmin":0,"indexScan":0,"indexHttp":0,"indexStreamInit":0,"indexStreamCatchup":0,"indexStreamMaint":0,"n1ql":8093}

          ,"hostname":"172.23.105.231"},{"services":

          {"mgmt":8091,"moxi":0,"kv":0,"capi":0,"kvSSL":0,"capiSSL":0,"mgmtSSL":18091,"projector":0,"indexAdmin":9100,"indexScan":9101,"indexHttp":9102,"indexStreamInit":9103,"indexStreamCatchup":9104,"indexStreamMaint":9105,"n1ql":0}

          ,"hostname":"172.23.105.245"},{"services":

          {"mgmt":8091,"moxi":0,"kv":0,"capi":0,"kvSSL":0,"capiSSL":0,"mgmtSSL":18091,"projector":0,"indexAdmin":9100,"indexScan":9101,"indexHttp":9102,"indexStreamInit":9103,"indexStreamCatchup":9104,"indexStreamMaint":9105,"n1ql":0}

          ,"hostname":"172.23.107.58"}]

          Show
          subhashni Subhashni Balakrishnan (Inactive) added a comment - yes 172.23.105.232 was rebalanced out. This was the latest config nodesExt":[{"services": {"mgmt":8091,"moxi":11211,"kv":11210,"capi":8092,"kvSSL":11207,"capiSSL":18092,"mgmtSSL":18091,"projector":9999,"indexAdmin":0,"indexScan":0,"indexHttp":0,"indexStreamInit":0,"indexStreamCatchup":0,"indexStreamMaint":0,"n1ql":0} ,"hostname":"172.23.105.230"},{"services": {"mgmt":8091,"moxi":0,"kv":0,"capi":0,"kvSSL":0,"capiSSL":0,"mgmtSSL":18091,"projector":0,"indexAdmin":0,"indexScan":0,"indexHttp":0,"indexStreamInit":0,"indexStreamCatchup":0,"indexStreamMaint":0,"n1ql":8093} ,"hostname":"172.23.105.231"},{"services": {"mgmt":8091,"moxi":0,"kv":0,"capi":0,"kvSSL":0,"capiSSL":0,"mgmtSSL":18091,"projector":0,"indexAdmin":9100,"indexScan":9101,"indexHttp":9102,"indexStreamInit":9103,"indexStreamCatchup":9104,"indexStreamMaint":9105,"n1ql":0} ,"hostname":"172.23.105.245"},{"services": {"mgmt":8091,"moxi":0,"kv":0,"capi":0,"kvSSL":0,"capiSSL":0,"mgmtSSL":18091,"projector":0,"indexAdmin":9100,"indexScan":9101,"indexHttp":9102,"indexStreamInit":9103,"indexStreamCatchup":9104,"indexStreamMaint":9105,"n1ql":0} ,"hostname":"172.23.107.58"}]
          Hide
          jmorris Jeff Morris added a comment -

          In the logs provided the client never bootstraps. One thing i am not clear about is what kind of node a client can bootstrap against (query, index, data). At the moment the client just uses whatever is provided in configuration without any bias as to what the node type is.

          Show
          jmorris Jeff Morris added a comment - In the logs provided the client never bootstraps. One thing i am not clear about is what kind of node a client can bootstrap against (query, index, data). At the moment the client just uses whatever is provided in configuration without any bias as to what the node type is.
          Hide
          jmorris Jeff Morris added a comment -

          The changes are in NodesExt, but the SDK is using the Nodes as the comparison to determine whether to swap out the internal nodes and connections. I'll have a fix ASAP.

          Show
          jmorris Jeff Morris added a comment - The changes are in NodesExt, but the SDK is using the Nodes as the comparison to determine whether to swap out the internal nodes and connections. I'll have a fix ASAP.

            People

            • Assignee:
              jmorris Jeff Morris
              Reporter:
              subhashni Subhashni Balakrishnan (Inactive)
            • 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.