スキップしてコンテンツを表示

Increased amount of writes after adding a replica to a non-empty table

0

Hi!

We've been using DynamoDB for quite some time already and never had any issues with it. We've never used global tables though. Yesterday we decided to add a new replica to a table in us-west-2. The table already contained ~60 million items totalling ~31 GB.

The whole process of adding a new replica was very smooth, taking around 2 hours, no problem there. The weird stuff started to happen after the replica was created. I expected that both replicas would have roughly the same amount of writes that would correspond to the number of writes done by our application. But some crazy things started to happen with the original replica. The amount of writes increased significantly there even though the traffic coming from our application didn't change (see the attached picture). And the application still works only with the original replica in us-west-2.

Does anyone know where these additional writes come from?

質問済み 6年前490ビュー

1回答
0

We've found the cause of the issue, so just in case anyone gets into the same trouble - the increased amount of writes is caused by propagation of TTL delete events.

回答済み 6年前

ログインしていません。 ログイン 回答を投稿する。

優れた回答とは、質問に明確に答え、建設的なフィードバックを提供し、質問者の専門分野におけるスキルの向上を促すものです。

関連するコンテンツ