Hi. I used CouchBase NodeJS SDK 2.6.10 previously and setting operationTimeout was something like this: const couchbase = require(‘couchbase’) var cluster = new couchbase.Cluster(‘couchbase://XXXXXXXXXXXXXXXXXXX’); cluster.authenticate(‘USERNAME’, ‘PASSWORD’) var bucket = cluster.openBucket(‘st…

Thank you @AV25242 sir for your consideration and please keep me updated if you find something. I’ll let you know if I find a solution myself.

Hello @kaiserindrajit first of all apologies for the delay as far as Timeout Settings is considered use the following , const myCluster = couchbase.connect('couchbase://…', { operationTimeout: ..., }) OR const myCluster = couchbase.connect('couchbase://...?operation_timeout=2500'); For other …

Thanks Arun. I’m using collection.get instead of couchbase.connect. Is this the proper usage for collection.get? Also, this might warrant another thread, but are there reasons (e.g. security or performance) to use couchbase.connect over collection.get? const cluster = new couchbase.Cluster(“couchba…

Hi @brankin welcome to the forums. On your first question about correct usage I believe you are asking if a timeout can be passed as an option upon connect vs get. ? The default timeout values are suitable for most environments, and should be adjusted only after profiling the expected latencies …

Than you @AV25242 sir. I really appreciate it. Last time I felt so bad about this problem. I tried to make the timeout work for analytics query for several days, so it doesn’t throw timeout error after 75sec. It didn’t work. So I stuck with the NodeJS SDK 2.6.10, where the timeouts actually worked. …

OK. So finally the solution is here with Couchbase NodeJS SDK 3.1.1. The coding approach isn’t much different than Couchbase NodeJS SDK 3.0.4, but it surely deals with that timeout problem. It has a problem though, but that can be easily handled. The first notable change in SDK 3.1.1 is that ‘couch…

[image] kaiserindrajit: And THIS WORKS. This surely does. This way, there’s no more timeout error after 75sec. Analytics queries on big datasets can easily be run for hours. But there’s a little problem. If we want to open a bucket to execute a certain operation and afterwards want to run this …

How to set operationTimeout in Couchbase NodeJS SDK 3X?

Node.js SDK

AV25242 June 23, 2020, 6:34pm 2

you seem to be correct, I do see query level timeouts but dont see a cluster level timeout options. I have reached out to the engineers to see if I am missing something. If not will open a ticket to get it addressed.

Topic		Replies	Views
Connect timeout in Node.js SDK 3.0 Node.js SDK node	1	1713	November 9, 2020
Python, Node SDK Query_timeout Setting Couchbase Server query , connections , timeout	6	801	December 11, 2023
Client timeout error Node.js SDK	2	2946	March 24, 2016
Couchbase NodeJS Error : Client-Side timeout exceeded for operation. Inspect network conditions or increase the timeout Node.js SDK node	19	8384	December 23, 2017
Nodejs sdk 3.1.1 - kvConnectTimeout is not being passed in options object from Cluster to Connection Node.js SDK connections	3	1630	November 8, 2021

How to set operationTimeout in Couchbase NodeJS SDK 3X?

Related topics