Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 1.2.6
    • Fix Version/s: None
    • Component/s: library
    • Labels:
      None

      Description

      At the moment it seems that the timeout values are only used on the initial connection to a Couchbase node, not on the servicing of operations.

      Comment from a customer:
      We had the problems in the WaitAny/WaitMultiple part of the BulkGet method. We saw that there is no timeout passed to the Wait methods. There is a time defined on the connections itself but it would be better if the WaitAny/WaitMultiple methods would have a timeout too.

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

        Activity

        Hide
        ingenthr Matt Ingenthron added a comment -

        Jeff: this is addressed in 2.x, correct?

        Show
        ingenthr Matt Ingenthron added a comment - Jeff: this is addressed in 2.x, correct?
        Hide
        jmorris Jeff Morris added a comment -

        Yes it is, there is a per operation timeout ClientConfiguration.DefaultOperationLifetime, which is the max amount of time given for an operation including any retries.

        -Jeff

        Show
        jmorris Jeff Morris added a comment - Yes it is, there is a per operation timeout ClientConfiguration.DefaultOperationLifetime, which is the max amount of time given for an operation including any retries. -Jeff

          People

          • Assignee:
            jmorris Jeff Morris
            Reporter:
            perry Perry Krug
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:

              Gerrit Reviews

              There are no open Gerrit changes