LogDNA keeps AWS lambda running until timeout

[rodrigopsasaki]

I am working on migrating an existing microservice cluster onto a serverless node stack based on AWS Lambda.

I was already using LogDNA before with no problems, but I ran into an issue when writing the lambdas. They all seemed to hang until the timeout, never completing successfully.

After some troubleshooting I figured out that if I set context.callbackWaitsForEmptyEventLoop to true the lambda finishes.

After some more digging I figured out that it was actually LogDNA keeping the lambda up and preventing it from completing.

Is this something that can be addressed? Or is it something in the core functionality of the library and I'll just have to figure out some way around it?

[shaynair]

This is likely related to #18

[ibnIrshad]

Yup I've reverted to logdna v1.1 because of this same issue. It's completely unacceptable that logdna hijacks SIGTERM

[cwp]

Calling cleanUpAll() before your handler returns will solve this.

[respectus]

Hi all,
We've made the decision to remove listening on signals since so many of our users are having issues. The library still exposes a cleanUpAll and cleanUp function, which users can opt-in to using if they so wish. Appreciate the feedback, do let me know if you experience any issues with logdna version 1.4.0, thanks!