0
我一直在單個表上測試Dynamic-DynamoDB，並且它不想縮減配置。任何人都可以看到我做錯了什麼嗎？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