Question

我一直在单个表上测试Dynamic-DynamoDB，并且它不想缩减配置。谁能看到我做错了什么？

这是一个周期的日志。我让它一夜之间运行......这个消息序列一直在继续。

2014-03-31 12:58:51,617 - dynamic-dynamodb - DEBUG - myTestTable - Currently provisioned read units: 25
2014-03-31 12:58:51,683 - dynamic-dynamodb - DEBUG - myTestTable - Currently provisioned read units: 25
2014-03-31 12:58:51,683 - dynamic-dynamodb - INFO - myTestTable - Consumed read units: 0%
2014-03-31 12:58:51,702 - dynamic-dynamodb - INFO - myTestTable - Read throttle count: 0
2014-03-31 12:58:51,719 - dynamic-dynamodb - DEBUG - myTestTable - Currently provisioned write units: 100
2014-03-31 12:58:51,779 - dynamic-dynamodb - DEBUG - myTestTable - Currently provisioned write units: 100
2014-03-31 12:58:51,779 - dynamic-dynamodb - INFO - myTestTable - Consumed write units: 0%
2014-03-31 12:58:51,806 - dynamic-dynamodb - INFO - myTestTable - Write throttle count: 0
2014-03-31 12:58:51,806 - dynamic-dynamodb - INFO - myTestTable - No need to change provisioning

并且，这是表格的配置：

[table: myTestTable]
reads-upper-threshold: 90
reads-lower-threshold: 30

increase-reads-with: 50
decrease-reads-with: 50

increase-reads-unit: percent
decrease-reads-unit: percent

min-provisioned-reads: 5
max-provisioned-reads: 25

writes-upper-threshold: 90
writes-lower-threshold: 30

increase-writes-with: 50
decrease-writes-with: 50

increase-writes-unit: percent
decrease-writes-unit: percent

min-provisioned-writes: 5
max-provisioned-writes: 100

#maintenance-windows: 22:00-23:59,00:00-06:00

sns-message-types: scale-up, scale-down

allow-scaling-down-reads-on-0-percent: true
allow-scaling-down-writes-on-0-percent: true

#always-decrease-rw-together: true

我还没有尝试过的唯一一件事就是设置维护时间。我假设当它们没有设置时，它会随时进行更新。

更新。我发现尝试在测试期间一夜之间发生的放大事件。显然，我已经处于最大状态，所以它没有做任何事情，正如我所料。我只是不明白为什么缩小规模不起作用。

2014-03-30 23:27:16,789 - dynamic-dynamodb - INFO - myTestTable - Consumed read units: 0%
2014-03-30 23:27:16,808 - dynamic-dynamodb - INFO - myTestTable - Read throttle count: 0
2014-03-30 23:27:16,827 - dynamic-dynamodb - DEBUG - myTestTable - Currently provisioned write units: 100
2014-03-30 23:27:16,880 - dynamic-dynamodb - DEBUG - myTestTable - Currently provisioned write units: 100
2014-03-30 23:27:16,880 - dynamic-dynamodb - INFO - myTestTable - Consumed write units: 117%
2014-03-30 23:27:16,901 - dynamic-dynamodb - INFO - myTestTable - Write throttle count: 0
2014-03-30 23:27:16,902 - dynamic-dynamodb - INFO - myTestTable - Reached provisioned writes max limit: 100
2014-03-30 23:27:16,902 - dynamic-dynamodb - INFO - myTestTable - No need to change provisioning
2014-03-30 23:27:17,104 - dynamic-dynamodb - DEBUG - Sleeping 300 seconds until next check
2014-03-30 23:32:17,277 - dynamic-dynamodb - DEBUG - myTestTable - Currently provisioned read units: 25
2014-03-30 23:32:17,353 - dynamic-dynamodb - DEBUG - myTestTable - Currently provisioned read units: 25
2014-03-30 23:32:17,354 - dynamic-dynamodb - INFO - myTestTable - Consumed read units: 0%
2014-03-30 23:32:17,375 - dynamic-dynamodb - INFO - myTestTable - Read throttle count: 0
2014-03-30 23:32:17,433 - dynamic-dynamodb - DEBUG - myTestTable - Currently provisioned write units: 100
2014-03-30 23:32:17,481 - dynamic-dynamodb - DEBUG - myTestTable - Currently provisioned write units: 100
2014-03-30 23:32:17,481 - dynamic-dynamodb - INFO - myTestTable - Consumed write units: 151%
2014-03-30 23:32:17,501 - dynamic-dynamodb - INFO - myTestTable - Write throttle count: 0
2014-03-30 23:32:17,501 - dynamic-dynamodb - INFO - myTestTable - Reached provisioned writes max limit: 100
2014-03-30 23:32:17,502 - dynamic-dynamodb - INFO - myTestTable - No need to change provisioning
2014-03-30 23:32:17,695 - dynamic-dynamodb - DEBUG - Sleeping 300 seconds until next check

Answer 1

似乎是版本中的错误。

https://github.com/sebdah/dynamic-dynamodb/issues/142

如果我还有其他问题，我会停止在这里发布这些内容并使用GitHub。 Sebdah很快回答。

Answer 2

在这种情况下，可能是一个错误，但是如果某些人仍然遇到这种错误，则有a limit of how many times per 24 hour period you can scale down a DynamoDB table。一旦达到该限制，DynamoDB将不允许您进一步缩减规模，并且如果您尝试再次要求这样做，则会引发错误。

Dynamic-DynamoDB没有按比例缩小

2 个答案: