Skip to content
This repository has been archived by the owner on Jan 8, 2021. It is now read-only.

Failing due to "body size too big" #4

Open
Tirano2150 opened this issue Aug 16, 2017 · 9 comments
Open

Failing due to "body size too big" #4

Tirano2150 opened this issue Aug 16, 2017 · 9 comments

Comments

@Tirano2150
Copy link

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

@tuxtek
Copy link

tuxtek commented Sep 14, 2017

We are seeing the same thing when running this on our accounts.
upload

@jkahn117
Copy link
Contributor

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.

@irfan1124
Copy link

@tuxtek Did your issue fixed ?? I am getting the same error...Please help me out.

@tuxtek
Copy link

tuxtek commented Sep 19, 2017

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. :)

@santhosh244
Copy link

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.

@santhosh244
Copy link

@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.

@devsecops-reetika
Copy link

I tried this solution but its not working . Please suggest

@symgryph
Copy link

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.

@mojimi
Copy link

mojimi commented Mar 8, 2019

Upload response to S3 and return presigned S3 link to client

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants