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

Ensure N1QL queries are retried after evicting invalid prepared statement

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved
    • Blocker
    • Resolution: Fixed
    • None
    • 2.5.2
    • None
    • None

    Description

      Caused by this change: https://github.com/couchbase/couchbase-net-client/commit/55f05bb65a075766fb5493386315178b6a4840cb

      CouchbaseRequestExecutor.RetryQueryEveryAsync retry behaviour does not use QueryClient.CheckRetry where query retry logic is located.

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. NCBC-1502 Fatal error: unexpected end of JSON input

          • Major - Major loss of function.
          • Resolved
          is triggered by

          Bug - A problem which impairs or prevents the functions of the product. NCBC-1502 Fatal error: unexpected end of JSON input

          • Major - Major loss of function.
          • Resolved
          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            Ascending order - Click to sort in descending order
            mike.goldsmith Michael Goldsmith added a comment -

            My mistake in re-adding CheckRetry and retrying directly in QueryClient. The intent was to use CouchbaseRequestExecutor for retry behaviour.

            mike.goldsmith Michael Goldsmith added a comment - My mistake in re-adding CheckRetry and retrying directly in QueryClient. The intent was to use CouchbaseRequestExecutor for retry behaviour.
            mike.goldsmith Michael Goldsmith added a comment -

            After discussing with Jeff, we're going revert change NCBC-1502 for 2.5.1 and move this ticket to 2.5.2 to ensure there are no regressions in moving the retry behaviour to the request executor level.

            mike.goldsmith Michael Goldsmith added a comment - After discussing with Jeff, we're going revert change NCBC-1502  for 2.5.1 and move this ticket to 2.5.2 to ensure there are no regressions in moving the retry behaviour to the request executor level.

            People

              mike.goldsmith Michael Goldsmith
              mike.goldsmith Michael Goldsmith
              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