Reputation: 403
We keep getting this exception in our app which has a scheduled job to read on a gloabl secondary index. Looks like it keeps backfilling periodically even though there were no changes on the table. The volumes on our table are quite low so a bit surprised to see this a few times a day. This is not a new index, so wondering should it not backfill only on insert/update of records. Anyone seen this before?
Upvotes: 38
Views: 22831
Reputation: 101
This error occurs when you newly create a GSI in dynamodb Table. wait for sometimes once it get created into the table you will not see the error see in below image it says Creating...
then hit your function you will not get an error
Upvotes: 10
Reputation: 1259
I just waited 30 seconds, the error was gone away automatically. I edited my dynamoDB table from my aws console directly, I think this temporary error originated from this.
Upvotes: 15
Reputation: 6301
It might be creating that GSI. Wait for sometime based on the amount of data in your DB. And this issue will go away.
Upvotes: 51
Reputation: 44
Try Detecting and Correcting Index Key Violations. I guess it is due to Index key Violation.
Upvotes: 0