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?
Asked
Active
Viewed 1.6k times
4 Answers
40
It might be creating that GSI. Wait for sometime based on the amount of data in your DB. And this issue will go away.
Khader M A
- 5,423
- 3
- 19
- 19
-
How long does it take for this to be fixed? We created the indexes and accessed it 3-4 hrs after the status was active – user2281204 Oct 15 '20 at 18:33
-
Index will be available in 10 minutes or less – Khader M A Nov 05 '20 at 13:54
9
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.
DanteDX
- 1,059
- 7
- 12
3
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...
it will be like
then hit your function you will not get an error
Praveen Singh
- 31
- 3
0
Try Detecting and Correcting Index Key Violations. I guess it is due to Index key Violation.
Rahul Rai
- 44
- 2
-
1"the key values in a global secondary index do not need to be unique".I have only one key on the index. It is not unique but it doesn't have to be. – Sateesh Dec 13 '19 at 13:14
-
-
check this --> https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/GSI.OnlineOps.ViolationDetection.html – Rahul Rai Dec 16 '19 at 11:14