AWS Lambda timing out due to open socket.

We are currently using your library in some of our AWS Lambda functions.

The way we use it is as a Stream in our bunyan logger. Even though everything seems to be working fine, and the logs reach our backend log aggregator servers, the Lambdas keep timing ou 100% of the time.

setting

context.callbackWaitsForEmptyEventLoop = false

seems to help to get rid of the timeouts, however the logs stop being sent to the backend.

We haven’t nailed down the issue 100% but it seems very likely that the timeouts are happening because of your library leaving connections/sockets open.

Can someone please advise?

[okkez]

Are we sure that all the messages will be sent if we close the sender like that?

Yes. We can wait ack response from Fluentd with requireAckResponse: true option.

'use strict';
const Console = require('console').Console;
var sender = require('fluent-logger').createFluentSender('tag.prefix', {
  host: 'localhost',
  port: 24224,
  timeout: 3.0,
  reconnectInterval: 600000, // 10 minutes
  requireAckResponse: true
});
var stdout = sender.toStream('stdout');
var stderr = sender.toStream('stderr');
var logger = new Console(stdout, stderr);
logger.log('this log record is sent to fluent daemon');
sender.end('end', {"message": "end of message!!"});

sender.end() w/o parameters will close socket immediately.

[okkez]

#91 is relevant to this issue.