Closed kght6123 closed 4 months ago
In our investigation, we identified the root cause of the issue to be Throughput exceeds the current capacity for one or more global secondary indexes.
It is important to note that DynamoDB auto scaling modifies provisioned throughput settings only when the actual workload stays elevated or depressed for a sustained period of several minutes. (Reference: https://docs.aws.amazon.com/wellarchitected/latest/serverless-applications-lens/capacity.html)
We understand the default DDB RCU scaling offered by the solution might not be ideal fit for your use case. In that case, we recommend going with provisioned RCUs or reducing refresh rate as you have done.
Based on the above, please note that we cannot implement this change in the default configuration of the solution.
Issue #, if available:
None.
Description of changes:
This is a hotfix because if it is long running and the number of Expired Tokens and Active Tokens is very high, the Lambda function can time out for more than 30 seconds when multiple people open the control panel.