Uploaded image for project: 'Couchbase Java Client'
  1. Couchbase Java Client
  2. JCBC-1223

Do not apply timeout if 0 on durability requirements

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved
    • Critical
    • Resolution: Fixed
    • 2.6.0
    • 2.6.1
    • None
    • None
    • 1

    Description

      This is a bug introduced in 2.6.0 which will always add a timeout operator to ops with durability requirements. This is always ok (> 0) but only if the async API is used without an explicit timeout we call .timeout() with 0 so the timer will fire very quickly. This needs to be fixed since it lets API calls like this time out prematurely: bucket.async().upsert(doc, PersistTo.MASTER); .. note the async(), on sync it's fine. Workaround for now is to always apply an explicit timeout as in bucket.async().upsert(doc, PersistTo.MASTER, 5, TimeUnit.SECONDS);

      Attachments

        For Gerrit Dashboard: JCBC-1223
        # Subject Branch Project Status CR V

        Activity

          There are no comments yet on this issue.

          People

            daschl Michael Nitschinger
            daschl Michael Nitschinger
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty