Skip to content
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

Getting weird "Table already exists" error when the table exists V.S. "Resources not found" error when table is deleted. #178

Open
terencelin opened this issue Sep 8, 2014 · 3 comments

Comments

@terencelin
Copy link

Hi there,

I have run into a weird error when I tried to create new tables on AWS.

Usually, it will create a new table automatically when table does not exist or when I change index keys, but recently it's giving me an error stated that "AWS::DynamoDB::Errors::ResourceNotFoundException".

So I created the table manually through AWS console and run it again, then this time it's giving me the error "(AWS::DynamoDB::Errors::ResourceInUseException) "Table already exists: ".

I have no idea what's going on here, a little help needed here please, thank you.

aws sdk : 1.29.1
dynamoid : 0.7.1

@ngordon17
Copy link

Did you check to make sure that the table you created in the AWS console wasn't still provisioning?

@nickdowse
Copy link

I had the same issue, and it went away after a few refreshes. Careful, if Sidekiq encounters this when it's starting up and initialising the class that you're using Dynamoid in then it will crash and will need to be restarted.

@jamp00
Copy link

jamp00 commented Dec 15, 2019

The solution for me was change the region in aws console

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants