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

Log message on timeout appears to lack instance

    XMLWordPrintable

Details

    • Task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 3.1.4
    • 3.1.5
    • None
    • None
    • 1

    Description

      When intentionally putting a system into a scenario where a cluster node fails, the client will expectedly log timeouts. I think it's also expected that it logs it with the instance identifier and the operation ID per RTO, but it looks like it's just showing the operation ID twice.

      The message from the exception is:

      Failed during upsert: The operation 1605/1605 timed out after 00:00:02.5000000. It was retried 1 times using Couchbase.Core.Retry.BestEffortRetryStrategy.
      

      Why is 1605 there twice?

      Attachments

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

        Activity

          There are no comments yet on this issue.

          People

            jmorris Jeff Morris
            ingenthr Matt Ingenthron
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty