Hi I have a simple AWS Lambda script running that uses the Node SDK (3.0) to do an insert. Everything works fine for about 2 hours, then I get the following unhandled promise rejection error: Error: LCB_ERR_TIMEOUT (201): A request cannot be completed until the user-defined timeout fired Re-dep…

Just to say - since this first post yesterday, I’ve gone through a lot of stuff, none of it has made any difference. The Lambda function, once started, stays ‘alive’ between invocations - all global variables are maintained, including the couchbase DB cluster connection, and the resulting bucket an…

Some further details. I’m deploying the code to the lambda function, and it runs perfectly for about 2 hours, roughly 82 invocations based around 1 container. Then Lambda dumps the container (perfectly normal) and a new container is created, obviously based around the same nodejs code. This time h…

It might be AWS related. They introduced some new networking for Lambda functions [image] Announcing improved VPC networking for AWS Lambda functions | Amazon Web... Update – November 28, 2019: We have fully rolled out the changes to the following additional Region to those mentioned belo…

[image] PavelN: TcpKeepAliveTime That’s interesting, thank you. How do I change this setting? Is it a server setting or something done when the cluster connection is established? I’m using the node sdk v3.0

I couldn’t find TcpKeepAlive for node.js. It’s definitely there for Java and .Net SDKs client settings. In node.js 2.6 sdk you could specify some timeout settings for operations. https://docs.couchbase.com/nodejs-sdk/2.6/client-settings.html . The 201 error is coming from the libcouchbase C librar…

Thanks - it would be really helpful to understand fully what this error means. What is being referred to by “the user-defined timeout” ? When I do a bucket.insert, I’m putting a “timeout:10000” option into the request? Is this the ‘user defined timeout’?

@mat01 , Thanks for making this post, I was having this issue intermittently for a long time, but your post led me in the right direction. The source of the error (Although really poorly documented and written) is covered here: Client Settings | Couchbase Docs (I am also using 3.0) but its the same. …

AWS Lambda Node Timeout Issue

Node.js SDK

mat01 March 10, 2020, 6:53pm 9

Hey Jeff, thank you so much for this.

Really helpful.

Topic		Replies	Views
Getting couchbase error: Client-Side timeout exceeded for operation Node.js SDK query , connections	12	7895	September 13, 2016
AWS Lambda timeout when quering Couchbase Node.js SDK	1	1631	December 13, 2017
AWS Lambda timeout Couchbase Server java	1	2451	October 12, 2017
AWS Lambda NodeJS bucket is idling out after 60 seconds Node.js SDK connections , timeout	3	1530	June 29, 2020
Serverless Provisioned Concurrency Issue with Couchbase Connection Node.js SDK connections , n1ql , index	5	2025	April 7, 2020

AWS Lambda Node Timeout Issue

Related topics