@pragnesh reported in #67 that:
sometime dynamic-dynamodb daemon crashed because dynamo table is just deleted which it has read just few second earlier and now it tried to update table throughput.
We should look into this.
@pragnesh, can you please provide a stack trace if you see this issue again?
i see following line, in log then it stopped working i am using regex configuration with one of table section start with
[f21_*] so, i think it got f21_16 table earlier by table list call, and one of our service perodically delete and create new table.
2013-10-14 05:44:00,066 - dynamic-dynamodb - INFO - f19_10 - Consumed write units: 0%
2013-10-14 05:44:00,067 - dynamic-dynamodb - INFO - f19_10 - Scaling down writes is not done when usage is at 0%
2013-10-14 05:44:00,067 - dynamic-dynamodb - INFO - f19_10 - No need to change provisioning
2013-10-14 05:44:00,867 - dynamic-dynamodb - ERROR - f21_16 - Table f21_16 not found
how to get stacktrace ?
Hmm, alright. I think that's good enough. But does Dynamic DynamoDB crash afterwards, or does it just give you that error?
it print error in log and daemon is not running after that
Fixed secure table fetching and minor syntax things #68
This should be resolved for most use cases now. I have released patch version 1.5.8