Minimum capacity ignored about dynamodb-lambda-autoscale

[tmitchel2]

Is the provisioned value starting off below the min and not getting incremented or above and min the going below? Do the logs say it wants to adjust the value but is not allowed?

[MaxxJag]

Increment works, but decrements doesn't respect minimum.
X is consuming 0 of 4 (0%) write capacity units so a decrement is WANTED but is DISALLOWED
Lower limit is 5, but it will take it down to 1 when it can.

[MaxxJag]

It seems to keep it at 4 for now. but if it gets over 5, it goes back down to 1. Might have a bug in how it brings it down. If I have sometime I'll look

[MaxxJag]

2016-11-24T20:41:42.402Z 680cf496-b286-11e6-9a0c-b39cf9c0695d Getting table description TABLE
2016-11-24T20:41:42.801Z 680cf496-b286-11e6-9a0c-b39cf9c0695d Getting table consumed capacity description TABLE
2016-11-24T20:41:43.222Z 680cf496-b286-11e6-9a0c-b39cf9c0695d Getting table update request TABLE
2016-11-24T20:41:43.222Z 680cf496-b286-11e6-9a0c-b39cf9c0695d TABLE is consuming 0.4 of 10 (4%) read capacity units
2016-11-24T20:41:43.222Z 680cf496-b286-11e6-9a0c-b39cf9c0695d TABLE is consuming 0.4 of 10 (4%) read capacity units so a decrement is WANTED and is ALLOWED
2016-11-24T20:41:43.223Z 680cf496-b286-11e6-9a0c-b39cf9c0695d TABLE is consuming 0.016666666666666666 of 10 (0.16666666666666666%) write capacity units
2016-11-24T20:41:43.223Z 680cf496-b286-11e6-9a0c-b39cf9c0695d TABLE is consuming 0.016666666666666666 of 10 (0.16666666666666666%) write capacity units so a decrement is WANTED and is ALLOWED
2016-11-24T20:41:43.240Z 680cf496-b286-11e6-9a0c-b39cf9c0695d Updating table TABLE
2016-11-24T20:41:43.309Z 680cf496-b286-11e6-9a0c-b39cf9c0695d Updated table TABLE
2016-11-24T20:41:43.309Z 680cf496-b286-11e6-9a0c-b39cf9c0695d Updated table TABLE
2016-11-24T20:42:42.923Z 8c23b1e7-b286-11e6-a0f5-dd0be00722cc Getting table description TABLE
2016-11-24T20:42:43.063Z 8c23b1e7-b286-11e6-a0f5-dd0be00722cc Getting table consumed capacity description TABLE
2016-11-24T20:42:43.481Z 8c23b1e7-b286-11e6-a0f5-dd0be00722cc Getting table update request TABLE
2016-11-24T20:42:43.482Z 8c23b1e7-b286-11e6-a0f5-dd0be00722cc TABLE is consuming 0.16666666666666666 of 1 (16.666666666666664%) read capacity units
2016-11-24T20:42:43.482Z 8c23b1e7-b286-11e6-a0f5-dd0be00722cc TABLE is consuming 0.16666666666666666 of 1 (16.666666666666664%) read capacity units
2016-11-24T20:42:43.482Z 8c23b1e7-b286-11e6-a0f5-dd0be00722cc TABLE is consuming 0.016666666666666666 of 1 (1.6666666666666667%) write capacity units
2016-11-24T20:42:43.482Z 8c23b1e7-b286-11e6-a0f5-dd0be00722cc TABLE is consuming 0.016666666666666666 of 1 (1.6666666666666667%) write capacity units

Happened, min is as set in config to 5 (as above) yet it took it down to 1

[MaxxJag]

I overwrote the config from DefaultProvisioner.json with my config and it now works. It seems to not be using my config. When I build it takes my config.env.production and zips into config.env. Perhaps I missed something...

[tmitchel2]

It is hardcoded to use DefaultProvisioner.json so unless you change the logic in that area you just need to alter DefaultProvisioner.json itself or point the code to another json file.