Cluster Query Settings API

queryCleanupClientAttempts
optional

When enabled, the Query service preferentially aims to clean up just transactions that it has created, leaving transactions for the distributed cleanup process only when it is forced to.

The node-level cleanupclientattempts setting specifies this property for a single node. When you change the cluster-level setting, the node-level setting is over-written for all nodes in the cluster.
Default : true
Example : false

boolean

queryCleanupLostAttempts
optional

When enabled, the Query service takes part in the distributed cleanup process, and cleans up expired transactions created by any client.

The node-level cleanuplostattempts setting specifies this property for a single node. When you change the cluster-level setting, the node-level setting is over-written for all nodes in the cluster.
Default : true
Example : false

boolean

queryCleanupWindow
optional

Specifies how frequently the Query service checks its subset of active transaction records for cleanup. Decreasing this setting causes expiration transactions to be found more swiftly, with the tradeoff of increasing the number of reads per second used for the scanning process.

The value for this setting is a string. Its format includes an amount and a mandatory unit, e.g. 10ms (10 milliseconds) or 0.5s (half a second). Valid units are:

The node-level cleanupwindow setting specifies this property for a single node. When you change the cluster-level setting, the node-level setting is over-written for all nodes in the cluster.
Default : "60s"
Example : "30s"

string (duration)

queryCompletedLimit
optional

Sets the number of requests to be logged in the completed requests catalog. As new completed requests are added, old ones are removed.

Increase this when the completed request keyspace is not big enough to track the slow requests, such as when you want a larger sample of slow requests.

Refer to Configure the Completed Requests for more information and examples.

The node-level completed-limit setting specifies this property for a single node. When you change the cluster-level setting, the node-level setting is over-written for all nodes in the cluster.
Default : 4000
Example : 7000

integer (int32)

queryCompletedThreshold
optional

A duration in milliseconds. All completed queries lasting longer than this threshold are logged in the completed requests catalog.

Specify 0 to track all requests, independent of duration. Specify any negative number to track none.

Refer to Configure the Completed Requests for more information and examples.

The node-level completed-threshold setting specifies this property for a single node. When you change the cluster-level setting, the node-level setting is over-written for all nodes in the cluster.
Default : 1000
Example : 7000

integer (int32)

queryLogLevel
optional

Log level used in the logger.

All values, in descending order of data:

DEBUG — For developers. Writes everything.

TRACE — For developers. Less info than DEBUG.

INFO — For admin & customers. Lists warnings & errors.

WARN — For admin. Only abnormal items.

ERROR — For admin. Only errors to be fixed.

SEVERE — For admin. Major items, like crashes.

NONE — Doesn’t write anything.

The node-level loglevel setting specifies this property for a single node. When you change the cluster-level setting, the node-level setting is over-written for all nodes in the cluster.
Default : "INFO"
Example : "DEBUG"

enum (DEBUG, TRACE, INFO, WARN, ERROR, SEVERE, NONE)

queryMaxParallelism
optional

Specifies the maximum parallelism for queries on all Query nodes in the cluster.

If the value is zero or negative, the maximum parallelism is restricted to the number of allowed cores. Similarly, if the value is greater than the number of allowed cores, the maximum parallelism is restricted to the number of allowed cores.

(The number of allowed cores is the same as the number of logical CPUs. In Community Edition, the number of allowed cores cannot be greater than 4. In Enterprise Edition, there is no limit to the number of allowed cores.)

The node-level max-parallelism setting specifies this property for a single node. When you change the cluster-level setting, the node-level setting is over-written for all nodes in the cluster.

In addition, there is a request-level max_parallelism parameter. If a request includes this parameter, it will be capped by the node-level max-parallelism setting.

Refer to Max Parallelism for more information.
Default : 1
Example : 0

integer (int32)

queryMemoryQuota
optional

Specifies the maximum amount of memory a request may use on any Query node in the cluster, in MB.

Within a transaction, this setting enforces the memory quota for the transaction. The transaction memory quota tracks only the delta table and the transaction log (approximately).

The node-level memory-quota setting specifies this property for a single node. When you change the cluster-level setting, the node-level setting is over-written for all nodes in the cluster.

In addition, there is a request-level memory_quota parameter. If a request includes this parameter, it will be capped by the node-level memory-quota setting.
Default : 0
Example : 4

integer (int32)

queryN1qlFeatCtrl
optional

N1QL feature control. This setting is provided for technical support only.

The node-level n1ql-feat-ctrl setting specifies this property for a single node. When you change the cluster-level setting, the node-level setting is over-written for all nodes in the cluster.

integer (int32)

queryNumAtrs
optional

Specifies the total number of active transaction records for all Query nodes in the cluster.

The node-level numatrs setting specifies this property for a single node. When you change the cluster-level setting, the node-level setting is over-written for all nodes in the cluster.

In addition, there is a request-level numatrs parameter. If a request includes this parameter, it will be capped by the node-level numatrs setting.
Default : 1024
Minimum value (exclusive) : 0
Example : 512

integer (int32)

queryPipelineBatch
optional

Controls the number of items execution operators can batch for Fetch from the KV.

The node-level pipeline-batch setting specifies this property for a single node. When you change the cluster-level setting, the node-level setting is over-written for all nodes in the cluster.

In addition, the request-level pipeline_batch parameter specifies this property per request. The minimum of that and the node-level pipeline-batch setting is applied.
Default : 16
Example : 64

integer (int32)

queryPipelineCap
optional

Maximum number of items each execution operator can buffer between various operators.

The node-level pipeline-cap setting specifies this property for a single node. When you change the cluster-level setting, the node-level setting is over-written for all nodes in the cluster.

In addition, the request-level pipeline_cap parameter specifies this property per request. The minimum of that and the node-level pipeline-cap setting is applied.
Default : 512
Example : 1024

integer (int32)

queryPreparedLimit
optional

Maximum number of prepared statements in the cache. When this cache reaches the limit, the least recently used prepared statements will be discarded as new prepared statements are created.

The node-level prepared-limit setting specifies this property for a single node. When you change the cluster-level setting, the node-level setting is over-written for all nodes in the cluster.
Default : 16384
Example : 65536

integer (int32)

queryScanCap
optional

Maximum buffered channel size between the indexer client and the query service for index scans. This parameter controls when to use scan backfill.

Use 0 or a negative number to disable. Smaller values reduce GC, while larger values reduce indexer backfill.

The node-level scan-cap setting specifies this property for a single node. When you change the cluster-level setting, the node-level setting is over-written for all nodes in the cluster.

In addition, the request-level scan_cap parameter specifies this property per request. The minimum of that and the node-level scan-cap setting is applied.
Default : 512
Example : 1024

integer (int32)

queryTimeout
optional

Maximum time to spend on the request before timing out (ns).

The value for this setting is an integer, representing a duration in nanoseconds. It must not be delimited by quotes, and must not include a unit.

Specify 0 (the default value) or a negative integer to disable. When disabled, no timeout is applied and the request runs for however long it takes.

The node-level timeout setting specifies this property for a single node. When you change the cluster-level setting, the node-level setting is over-written for all nodes in the cluster.

In addition, the request-level timeout parameter specifies this property per request. The minimum of that and the node-level timeout setting is applied.
Default : 0
Example : 500000000

integer (int64)

queryTxTimeout
optional

Maximum time to spend on a transaction before timing out. This setting only applies to requests containing the BEGIN TRANSACTION statement, or to requests where the tximplicit parameter is set. For all other requests, it is ignored.

The value for this setting is a string. Its format includes an amount and a mandatory unit, e.g. 10ms (10 milliseconds) or 0.5s (half a second). Valid units are:

Specify 0ms (the default value) to disable. When disabled, no timeout is applied and the transaction runs for however long it takes.

The node-level txtimeout setting specifies this property for a single node. When you change the cluster-level setting, the node-level setting is over-written for all nodes in the cluster.

In addition, there is a request-level txtimeout parameter. If a request includes this parameter, it will be capped by the node-level txtimeout setting.
Default : "0ms"
Example : "0.5s"

string (duration)

queryTmpSpaceDir
optional

The path to which the indexer writes temporary backfill files, to store any transient data during query processing.

The specified path must already exist. Only absolute paths are allowed.

The default path is var/lib/couchbase/tmp within the Couchbase Server installation directory.
Example : "/opt/couchbase/var/lib/couchbase/tmp"

string

queryTmpSpaceSize
optional

The maximum size of temporary backfill files (MB).

Setting the size to 0 disables backfill. Setting the size to -1 means the size is unlimited.

The maximum size is limited only by the available disk space.
Default : 5120
Example : 2048

integer (int32)

queryUseCBO
optional

Specifies whether the cost-based optimizer is enabled.

The node-level use-cbo setting specifies this property for a single node. When you change the cluster-level setting, the node-level setting is over-written for all nodes in the cluster.

In addition, the request-level use_cbo parameter specifies this property per request. If a request does not include this parameter, the node-level setting is used, which defaults to true.
Default : true
Example : false

boolean

queryCurlWhitelist
optional

An object which determines which URLs may be accessed by the CURL() function.

Access

all_access
required

Defines whether the user has access to all URLs, or only URLs specified by the access list.

This field set must be set to false to enable the allowed_urls and disallowed_urls fields.

Setting this field to true enables access to all endpoints.
Default : false

boolean

allowed_urls
optional

An array of strings, each of which is a URL to which you wish to grant access. Each URL is a prefix match. The CURL() function will allow any URL that starts with this value.

For example, if you wish to allow access to all Google APIs, add the URL https://maps.googleapis.com to the array. To allow complete access to localhost, use http://localhost.

Note that each URL must include the port, protocol, and all other components of the URL.

< string > array

disallowed_urls
optional

An array of strings, each of which is a URL that will be restricted for all roles. Each URL is a prefix match. The CURL() function will disallow any URL that starts with this value.

If both allowed_urls and disallowed_urls fields are populated, the disallowed_urls field takes precedence over allowed_urls.

Note that each URL must include the port, protocol, and all other components of the URL.

< string > array