Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DynamoDB tables replication blocked with lambda out of memory #13

Open
RichardLeeY opened this issue Nov 29, 2022 · 0 comments
Open

DynamoDB tables replication blocked with lambda out of memory #13

RichardLeeY opened this issue Nov 29, 2022 · 0 comments

Comments

@RichardLeeY
Copy link

RichardLeeY commented Nov 29, 2022

We build CDC solution on AWS Account.
For some frequently updated DDB tables , we find that the target dynamoDB table has no data imported. We checked the lambda logs . The logs show as follow
lambda-error

As we can see, the lambda default 128M memory are used up. we update lambda memory size by aws cli and the replication recovered.

aws lambda update-function-configuration \ --function-name my-function \ --memory-size 256

Solutions Suggestion:
1.Expose lambda Memory size as parameter in sam template.

2.furthor more, It will be better if we add sns notification with lambda error logs ,So that people can receive alarm mail in time.

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

No branches or pull requests

1 participant