...
| Setting | Description | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Bucket Configuration | |||||||||||
Bucket Name | Enter the bucket that you want to access in Couchbase in this field. | ||||||||||
| Bucket User | Enter the user who has access rights to the bucket. | ||||||||||
User Password | Enter the password for the user who has access to the bucket. | ||||||||||
| Parameterized | When enabled, here you may enter parameterized bucket configuration. | ||||||||||
| Cluster Connectivity | |||||||||||
Operation Timeout (ms) | Enter the number of milliseconds after which you want Couchbase "CRUD" operations, that is, create, read, update, and delete, to timeout. Setting a lower value than the default 1000 ms may have a positive impact on throughput performance. However, if the value is set too low, indicated by a large number of operation timeouts errors in the EC logs, a lower throughput can be expected. As mentioned, this value is used for timing out CRUD operations in Couchbase. This means that the system sends a request towards Couchbase and if an answer is not returned in time, the operation fails, and the system is no longer waiting for an answer. | ||||||||||
Retry Interval Time (ms) | Enter the time interval, in milliseconds, that you want to wait before trying to read the cluster configuration again after a failed attempt. In other words, in case a request sent to Couchbase returns an unsuccessful answer, the number specified here is the time that the system waits before retrying the same request. | ||||||||||
Max Number Of Retries | Enter the maximum number of retries. This is the number of retries the system does before treating the Couchbase operation as failed. | ||||||||||
| Enable Security | |||||||||||
| Parameterized | |||||||||||
| Security Profile |
| ||||||||||
| Cluster Nodes | |||||||||||
Cluster Nodes | In this section, add IP addresses/hostnames of at least one of the nodes in the cluster. This address information is used by the Couchbase profile to connect to the cluster at workflow start, and to retrieve the IP addresses of the other nodes in the cluster. If the first node in the list cannot be accessed, the Couchbase profile will attempt to connect to the next one in order. This is repeated until a successful connection can be established. Hence it is not necessary to add all the nodes, but it is good practice to do so for a small cluster. For example, if there are just three nodes, you should add all of them. | ||||||||||
...