Closed mithun35h closed 12 months ago
Hello, @mithun35h and thank you for opening this issue. Can you clarify what your lambda timeout is currently set to? I'm curious to see if it's still at the default setting of 3 seconds and if increasing it to something like 10 seconds changes the behavior at all.
its set to 30s and memory is increased to 512mb
I did enable the logs in opensearch as well, i don't see the timeout issue there in either index logs or application logs of opensearch
I did increase the opensearch instance sizes and added a 2 nodes to make sure health is green
This was due to indexing rate error, i optimised the customer by reducing the replicas and number of shards
And also increase the timeout to even higher
Time out error are not seen any more
@mithun35h, great to hear you got this sorted out! If there's further issues, feel free to comment back or open a new issue (if related to another error/problem).
Before opening, please confirm:
JavaScript Framework
Not applicable
Amplify APIs
DataStore
Amplify Categories
api
Environment information
Describe the bug
using the @searchable directive in schema graphql, creates a lambda to stream from Dynamo DB to Opensearch
We often see this lambda throwing timeout error, which makes the data out of sync and missing between dynamodb to opensearch
Expected behavior
No Timeout issues
Reproduction steps
NA
Code Snippet
Log output
aws-exports.js
No response
Manual configuration
No response
Additional configuration
No response
Mobile Device
No response
Mobile Operating System
No response
Mobile Browser
No response
Mobile Browser Version
No response
Additional information and screenshots
No response