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
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
As we can see, the lambda default 128M memory are used up. we update lambda memory size by aws cli and the replication recovered.
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
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.
The text was updated successfully, but these errors were encountered: