-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
Closed
Labels
aws:lambdaAWS LambdaAWS Lambdaaws:sqsAmazon Simple Queue ServiceAmazon Simple Queue Servicestatus: backlogTriaged but not yet being worked onTriaged but not yet being worked ontype: bugBug reportBug report
Description
Is there an existing issue for this?
- I have searched the existing issues
Current Behavior
Multiple lambda environments are spawned in parallel
Expected Behavior
A single lambda environment should handle the messages sequentially.
How are you starting LocalStack?
Custom (please describe below)
Steps To Reproduce
Scenario:
- Create a lambda with a set timeout (e.g. 30s) + fifo queue + disabled event source mapping
- Send 5 messages to the queue with the same message group id ( => guarantees that they should be processed one by one in-order)
- enable the event source mapping so that the Lambda service can start processing the messages
- Wait for some time ( e.g. 90s) and check how many log streams have been created
Environment
-Anything else?
No response
wzomer, whummer and vajsm
Metadata
Metadata
Assignees
Labels
aws:lambdaAWS LambdaAWS Lambdaaws:sqsAmazon Simple Queue ServiceAmazon Simple Queue Servicestatus: backlogTriaged but not yet being worked onTriaged but not yet being worked ontype: bugBug reportBug report