Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. MB-39682

doGetBulk() to not retry errNoPool

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • Cheshire-Cat, 6.0.4, 6.5.1
    • 7.1.0
    • query
    • None
    • Untriaged
    • 1
    • Unknown

    Description

      There are situations where a bucket connection pool gets closed and refreshed.
      In this case getting a connection from a pool will return a "no connection pool" error until connections are moved from the old pool to the new pool, which will probably take a minute.

      There is little point in doBulkGet() in doing a retry because it will likely go through all the retries very quickly and fail, and hog the CPU in the process.
      noErrPool should abort rather than retry, or at the very least back off.

      Attachments

        Issue Links

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

          Activity

            People

              isha Isha Kandaswamy (Inactive)
              marco.greco Marco Greco
              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