New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Under some circumstances Dynamic DynamoDB crashes when table is deleted #68

Closed
sebdah opened this Issue Oct 17, 2013 · 5 comments

Comments

Projects
None yet
2 participants
@sebdah
Owner

sebdah commented Oct 17, 2013

@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.

@ghost ghost assigned sebdah Oct 17, 2013

@sebdah

This comment has been minimized.

Owner

sebdah commented Oct 17, 2013

@pragnesh, can you please provide a stack trace if you see this issue again?

@pragnesh

This comment has been minimized.

Contributor

pragnesh commented Oct 17, 2013

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 ?

@sebdah

This comment has been minimized.

Owner

sebdah commented Oct 18, 2013

Hmm, alright. I think that's good enough. But does Dynamic DynamoDB crash afterwards, or does it just give you that error?

@pragnesh

This comment has been minimized.

Contributor

pragnesh commented Oct 18, 2013

it print error in log and daemon is not running after that

@sebdah

This comment has been minimized.

Owner

sebdah commented Oct 18, 2013

This should be resolved for most use cases now. I have released patch version 1.5.8

@sebdah sebdah closed this Oct 18, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment