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

Provide more detail on "Unable to locate node" errors

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Cannot Reproduce
    • Affects Version/s: 1.2.2
    • Fix Version/s: backlog-1.0
    • Component/s: docs, library
    • Labels:
      None
    No reviews matched the request. Check your Options in the drop-down menu of this sections header.

      Activity

      Hide
      TimSmith Tim Smith (Inactive) added a comment -

      For clarity, the desired change is in the library itself, to provide info in the error message about what host lost the connection, whether there was a corrupt cluster map or just couldn't connect to any of the hosts, etc. Currently the error provides no insight into where the problem may lie. The developer can assume there may be some networking problem, but no pointer about which node is to blame, etc.

      Show
      TimSmith Tim Smith (Inactive) added a comment - For clarity, the desired change is in the library itself, to provide info in the error message about what host lost the connection, whether there was a corrupt cluster map or just couldn't connect to any of the hosts, etc. Currently the error provides no insight into where the problem may lie. The developer can assume there may be some networking problem, but no pointer about which node is to blame, etc.
      Hide
      jmorris Jeff Morris added a comment - - edited

      Hi Morrie -

      The "unable to locate node" message happens when something outside of the client (usually network) temporarily drops the clients connection. Another cause is when an application running on the client blocks the streaming http connection - Fiddler (http://www.telerik.com/fiddler) is a common culprit on windows.

      Another common cause is when the hostname in the configuration is wrong or the bucket doesn't exist (if I remember correctly).

      -Jeff

      Show
      jmorris Jeff Morris added a comment - - edited Hi Morrie - The "unable to locate node" message happens when something outside of the client (usually network) temporarily drops the clients connection. Another cause is when an application running on the client blocks the streaming http connection - Fiddler ( http://www.telerik.com/fiddler ) is a common culprit on windows. Another common cause is when the hostname in the configuration is wrong or the bucket doesn't exist (if I remember correctly). -Jeff
      Hide
      morrie Morrie Schreibman added a comment -

      Marking as resolved; support ticket was long ago closed

      Show
      morrie Morrie Schreibman added a comment - Marking as resolved; support ticket was long ago closed
      Hide
      morrie Morrie Schreibman added a comment -

      closing; problem has not reproduced at customer site.

      Show
      morrie Morrie Schreibman added a comment - closing; problem has not reproduced at customer site.

        People

        • Assignee:
          jmorris Jeff Morris
          Reporter:
          john John Zablocki (Inactive)
        • Votes:
          5 Vote for this issue
          Watchers:
          8 Start watching this issue

          Dates

          • Created:
            Updated:
            Resolved:

            Gerrit Reviews

            There are no open Gerrit changes