-
Notifications
You must be signed in to change notification settings - Fork 41
Failing due to "body size too big" #4
Comments
This error seems to be related to Lambda payload size. One option would be to try reducing the Amazon Kinesis Firehose ES Buffer Size and/or Interval, this should result in the payload being reduced. If you have an opportunity to test, please respond back. |
@tuxtek Did your issue fixed ?? I am getting the same error...Please help me out. |
I have been tied up firefighting and unable to get back to it yet. I will try it out by tomorrow and let you know. :) |
I had same issue couple of months and did the same [ set ES buffer size (MB) value to 1] and all the invocation errors stopped and flow logs works perfectly. |
@Tirano2150 / @tuxtek : With your data you should also get an error on geographical data check which has per hour limitation. Even i had that issue and commented our the geo check function. if you see invocation errors check this as well. |
I tried this solution but its not working . Please suggest |
I tried it too, it kind of works if things are really slow. But it doesn't seem to work otherwise. Spent several hours with aws on phone to no avail. Oh well. |
Upload response to S3 and return presigned S3 link to client |
When working with larger networks the decorator fails due to the response "body size is too long" (response over 6MB).
I've observed this when decorating 11K + items
The text was updated successfully, but these errors were encountered: