- 最新
- 最多得票
- 最多評論
Hi - Unintentional recursive loops can result in unexpected charges being billed to your AWS account. Loops can also cause Lambda to scale and use all of your account's available concurrency. To help reduce the impact of unintentional loops, Lambda can detect certain types of recursive loops shortly after they occur. When Lambda detects a recursive loop, it stops your function being invoked and notifies you.
To prevent a reoccurrence of a recursive loop that Lambda has broken, do the following:
- Reduce your function's available concurrency to zero, which throttles all future invocations.
- Remove or disable the trigger or event source mapping that's invoking your function.
- Identify and fix code defects that write events back to the AWS resource that's invoking your function. A common source of defects occurs when you use variables to define a function's event source and target. Check that you're not using the same value for both variables.
Additionally, if the event source for your Lambda function is an Amazon SQS queue, then consider configuring a dead-letter queue on the source queue.
If you have a Basic Support plan and require one-on-one technical support, you can upgrade your Support plan. For more information, see How do I change my AWS Support plan?
相關內容
- AWS 官方已更新 3 年前
- AWS 官方已更新 3 年前
- AWS 官方已更新 1 年前
- AWS 官方已更新 3 年前
Thanks, right now this feature of loop detection is disabled. Is there any way i can request to re-enable this without upgrading my support plan?