readme suggests done() which is incorrect

On the readme, it says to call done();

Following this, 3 times I managed to exhaust all database connections. The link under the example suggests done(client); which correctly closes the connection.

I think this is a possible documentation error.

---

Basically we need the connection timeout handler to live in a separate process to make the lambda function freezable. That should solve the termination timeout issue (in theory).

How lambda handles re-use is described here in detail: https://aws.amazon.com/blogs/compute/container-reuse-in-lambda/ Pay attention to the last section in particular.

[lukas-gitl]

Final Note for now: We stopped using connection pooling. Amazon handles this very badly. Basically we now always call client.release(true) to terminate any connection.

This will be best practice until Amazon improves their container handling with Lambda. If you don’t do this you are dealing with all sorts of issues (one is that many open connections are just sticking around).

[lukas-gitl]

Yep, setting context.callbackWaitsForEmptyEventLoop = false; seems to resolve this.

Can you confirm @brianc ?