I set up my tables and then realized that one of them would need a lot more reads, so I added a min_provisioned_reads for that table. I expected it to automatically scale up, but it didn't. Based on the code, I think min_provisioned_reads is only consulted if we've already decided to scale the table. This surprised me.
Thanks for the report.
It seems like a bug (and I come to the same conclusion as you when looking in the code). I'll dig into it.
Now explicitly scaling up to min-provisioned-* #202
This has now been fixed and released in version 1.18.4. Please give it a try.
Thanks again for the bug report
Fix confirmed, thanks!
It looks like this patch doesn't respect Dynamo's "you can only increase the provisioning by 100% at a time" restriction. I have a table that it's trying to adjust from a throughput of 3 directly to 10 (which is the minimum I set), but it fails every time because Dynamo will only let it be adjusted up to 6.
You're right, I'll look into that. Thanks for the report!