You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 25, 2022. It is now read-only.
I have a Kinesis Stream in one region connected to a Kinesis Stream in another region via this project. It appears that the records in the destination stream have been concatenated together, resulting in records that are too large for my final processing to work with. I can't figure out how this is happening though or how to stop it. Any ideas?
The text was updated successfully, but these errors were encountered:
This did not fix my problem, but it did fix WriteProvisionedThroughputExceeded issues I was having where it seemed no matter how many more shards I added, I could never get that value to zero after I started using aws-lambda-fanout. This also was causing the number of PutRecords.Success to always be far below PutRecords.Records. By commenting out that line and setting that variable to zero, I was able to fix this. I think that change should be merged into this project, as right now the collapse value is being set to API for Kinesis Streams (https://github.com/awslabs/aws-lambda-fanout/blob/0e7ffd73228f0832ae55939937cf8564f6a063f0/lib/configuration.js#L114), which doesn't seem to have meaning anywhere else in the code and may be a bug.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have a Kinesis Stream in one region connected to a Kinesis Stream in another region via this project. It appears that the records in the destination stream have been concatenated together, resulting in records that are too large for my final processing to work with. I can't figure out how this is happening though or how to stop it. Any ideas?
The text was updated successfully, but these errors were encountered: