Thanks for the reply. Actually my Lambda consumers are consuming batched
messages from a Kinesis queue in AWS, process them, and send results to Kafka.
Even with 'reserve concurrency' AWS will frequently stop and
re-initiate/-invoke the function for different batches - resulting in
Even if it is not a memory leak it is not a good practice. You can put the
messages on SQS and have a lambda function listening to the SQS queue with
reserve concurrency to put it on Kafka
> Am 15.08.2019 um 08:52 schrieb Tianning Zhang
> :
>
> Dear all,
>
> I am using Amazon AWS Lambda
