const dax = new AmazonDaxClient({endpoints: [process.env.DAX_ENDPOINT], region: env.AWS_REGION || 'us-east-1', requestTimeout: 1000, maxRetryDelay: 1000, httpOptions: { timeout: 1000} });
export const ddbDaxClient = new DynamoDB.DocumentClient({
service: dax as unknown as AWS.DynamoDB,
maxRetryDelay: 1000,
requestTimeout: 1000,
httpOptions: { timeout: 1000}
})
I'm trying to set a custom timeouts which is supported by DocumentClient, however when I set it on the DaxClient it is not getting passed to the DocumentClient. Setting it on the DocumentClient is also not working.
All I want to do is make it so Dax does not retry a bunch of times, but overriding this internal retry logic does not seem possible. Any help I can get would be appreciated.
Here is the service.config that i can log. As you can see the timeouts are there, so are the retries, but its completely ignored.
Update. It seems like after the first invocation of the lambda, the timeout is respected in following invocations, altho that might not be my configs doing
Hoping I might get some help with this.
I'm trying to set a custom timeouts which is supported by DocumentClient, however when I set it on the DaxClient it is not getting passed to the DocumentClient. Setting it on the DocumentClient is also not working.
All I want to do is make it so Dax does not retry a bunch of times, but overriding this internal retry logic does not seem possible. Any help I can get would be appreciated.
Here is the service.config that i can log. As you can see the timeouts are there, so are the retries, but its completely ignored.