Skip to content
This repository has been archived by the owner on Oct 25, 2022. It is now read-only.

Seeing the following error "Record too large to be pushed to target 'reconnectToDEV' of type 'kinesis'" #37

Open
joebowen opened this issue Nov 14, 2019 · 0 comments

Comments

@joebowen
Copy link

Hi,

I'm seeing the following error in my kinesis fanout handler deployment:

'Record too large to be pushed to target 'reconnectToDEV' of type 'kinesis''

The system is setup to take a single record from a kinesis stream (batch size == 1) and push it to a different kinesis stream.

So the question is, how is a single record from a kinesis stream too big to put into a different kinesis stream?

I suspect there is an issue with how the fanout handler is calculating the max allowed size from this line:
https://github.com/aws-samples/aws-lambda-fanout/blob/master/fanout.js#L63

AWS Support suggested that I open up a github issue, ticket #6553563951

Thank you,

Joe Bowen

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

1 participant