Skip to content
This repository has been archived by the owner on Dec 1, 2022. It is now read-only.

Odd logging message & failure to increase throughput capacity #42

Open
awinder opened this issue Jan 5, 2017 · 1 comment
Open

Odd logging message & failure to increase throughput capacity #42

awinder opened this issue Jan 5, 2017 · 1 comment

Comments

@awinder
Copy link

awinder commented Jan 5, 2017

I'm getting the following types of cloudwatch logs and inability to increase Read/Write Capacity past 100:

{{tablename}} is consuming 96.725 of 100 (96.725%) read capacity units and is above maximum threshold of 75% so an increment is not required

Maybe I'm just reading this incorrectly but why does this condition not require an increment? I'm thinking that possibly the config I'm using has a 100 unit ceiling, but that's not quite reflected in this message.

@tmitchel2
Copy link
Member

100 is the default maximum so that is probably the reason, but you are right the message is not correct in this case. Ill leave open to correct this as i wanted to improve this area.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants