Closed wafflespeanut closed 1 week ago
@wafflespeanut thanks for reporting this bug. I created a PR to fix it.
We see that the issue is during lambda invocation, but to be sure, could you also share trace logs that show the service name and operation name that run into this issue? An example line would look like
DEBUG invoke{service=s3 operation=GetObject sdk_invocation_id=8555156} ...
I do find a debug log line that looks like this:
[DEBUG] invoke; service=lambda operation=Invoke sdk_invocation_id=8300105
Do you want me to paste all log lines surrounding this as well?
Do you want me to paste all log lines surrounding this as well?
No, what you provided with us looks good. Thank you!
Disabling StalledStreamProtection for Lambda was released yesterday.
Comments on closed issues are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.
Describe the bug
I'm facing
ThroughputBelowMinimum
whenever I invoke lambda. Pretty much looks like #1141, which has been marked as resolved, but when I use disable stalled stream protection, I'm able to get past it and actually get a response.Expected Behavior
Succeeding Lambda function invocation whenever I want.
Current Behavior
Significant proportion of failures over successful requests
Reproduction Steps
Continuous lambda invocation.
Possible Solution
Disable StalledStreamProtection in client config.
Additional Information/Context
No response
Version
Environment details (OS name and version, etc.)
MacOS 14.5 Sonoma (Silicon chip)
Logs