Open bob-walker-nhs opened 6 months ago
I don't know the threshold of where this happens. A file of 16,731,558 bytes worked fine, so it's somewhere between those numbers, appreciate that doesn't narrow it down enough.
we face same problem by resolving increase memory of lambda now. Any better suggestion? Beside the terraform is not allow us to control lambda memory size. Is it by purpose or just simply missing variable ?
Sending a text file of 60,442,799 bytes causes the
mesh-fetch-message-chunk
Lambda to get killed by the AWS execution environment. e.g.:This then becomes unresolvable, because the message never gets acknowledged, and the
mesh-get-messages
Lambda continues to identify the offending message as available. The only way I could resolve it was to log into MESHUI and download the message so that it would get acked. This is probably not as easy in Production. Whilst in this state, our system is unusable.Tracking here to ask the questions: