Uploaded image for project: 'Couchbase Documentation'
  1. Couchbase Documentation
  2. DOC-8517

Clarify that cluster-level queryTxTimeout overrides the SDK

    XMLWordPrintable

Details

    • DOC-2021-Jun06-S11, DOC-2021-Jun20-S12, DOC-2021-Jul04-S13, DOC-2021-Jul18-S14, DOC-2021-Nov07-S22, DOC-2021-Nov21-S23, DOC-2021-Dec05-S24, DOC-2021-Dec19-S25, DOC-2021-Dec31-S26, DOC-2022-S1, DOC-2022-S2, DOC-2022-S3, DOC-2022-S4, DOC-2022-S5, DOC-2022-S6, DOC-2022-S7, DOC-2022-S8, DOC-2022-S9, DOC-2022-S10, DOC-2022-S11, DOC-2022-S12, DOC-2022-S13, DOC-2022-S14, DOC-2022-S15, DOC-2022-S16, DOC-2022-S17, DOC-2022-S18, DOC-2022-S19
    • 1

    Description

      We should document the fact that queryTxTimeout, specified at the cluster level, acts as a unconditional upper bound on all transactional statements that are executed. This does not match with the existing SDK precedence where overriding timeouts is possible at any level. See the linked TXNJ for additional information.

      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

            richard.smedley Richard Smedley
            brett19 Brett Lawson
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty