1 Resposta
- Mais recentes
- Mais votos
- Mais comentários
1
My assumption here is that your remote table does not have enough capacity to commit all the items and is failing due to excessive throttling. You do not have this issue when committing to local.
To diagnose, check your tables metrics section in the AWS web console and have a look for write throttling events. If you see a spike in throttles at the same time as your commit it indicates you must increase your tables capacity (WCU).
Conteúdo relevante
- AWS OFICIALAtualizada há 8 meses
- AWS OFICIALAtualizada há 2 anos
- AWS OFICIALAtualizada há um ano
Thanks for your advice. I will check the metrics and increase the capacity.
I assume you're correct in that it's a throttling issue, but how do you fix this? NoSQL Workbench creates the table for you, and then automatically puts the items. If you try to 'Commit to Amazon DynamoDB' again, it fails because the table already exists. There is no "window" to increase the table capacity.
That is correct and its something the NoSQL Workbench team are aware of. It should be resolved in future releases.