내용으로 건너뛰기

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년 전

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

관련 콘텐츠