dynamodb table stuck in creating

0

I am creating a few global tables in dynamodb (from CDK). After creating some tables without problems, one of the table was created on the main region and got stuck in "updating" while a replica remained stuck in "Creating". This remained blocked for the last ~16 hours without a timeout, and I can't find a way to cancel the creation from the console (or otherwise). Is there a way to delete/cancel this type of hanging operations?

Thank you!

4 Answers
1

No unfortunately there is no way to cancel the request, you must first let it complete before removing the replica. If your source region has a large amount of data, then it can take several hours to replicate the data to other regions. Furthermore, your source region is still fully active to serve traffic while in an Updating state.

If your table is still stuck, then please reach out to customer services who can assist with the issue.

https://aws.amazon.com/contact-us/

profile pictureAWS
EXPERT
answered 10 months ago
0

Hi, the table is empty. The incident happened in the initial creation: created in CDK:

new CfnGlobalTable(scope, tableName, new CfnGlobalTableProps { [......] Replicas = [....], }

So the table in the main region was created and started creating the replica in the first region. The replica is stuck in "Creating" and after a while the stacks started to rollout and got deleted. And what is left is these 2 tables (the main region one in "updating" and the replica in "creating"). Of course the dynamodb stack failed to delete, but then i deleted it ok by skipping the respective table. At this moment it would be around 20hours - what is considered to be a maximum timeout? Thank you!

answered 10 months ago
  • Its very likely you are missing permissions to create the replica for Global Table and thats why its stuck in creating state. As mentioned, reach out to Customer Services to have the issue resolved.

0

Deploying the same stack (no change, except different table names), with same user (which is full admin) worked ok. Also the first time a few tables and replicas were created ok before getting stuck. So it doesn't seem like an user permission error.

Also, we have basic support, which doesn't allow me to request tech support. But this issue, as mentioned, seems more like a bug on AWS side rather than a personal support request. Is there another section where i need to address my request to?

Thank you!

answered 10 months ago
  • You do not need tech support, customer services should sort the issue out for you.

0

Thank you!

answered 10 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions