Skip to content

Investigate and fix 500s when writing to Dynamo #85

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
jml opened this issue Nov 2, 2016 · 6 comments
Closed

Investigate and fix 500s when writing to Dynamo #85

jml opened this issue Nov 2, 2016 · 6 comments
Assignees
Milestone

Comments

@jml
Copy link
Contributor

jml commented Nov 2, 2016

We are getting a fairly constant stream of 500s from Dynamo when we attempt to write to it (~3-4qps on dev).

We should understand what's causing this & fix it. https://github.com/weaveworks/monitoring/issues/12 will help.

@jml
Copy link
Contributor Author

jml commented Nov 2, 2016

Might be related to #61, but too early to say.

@jml jml mentioned this issue Nov 2, 2016
@jml jml modified the milestone: KubeCon 2016 Nov 4, 2016
@tomwilkie
Copy link
Contributor

According to loggly, 90% of the log lines (and therefore errors) are ProvisionedThroughputExceededException.

@tomwilkie tomwilkie self-assigned this Nov 6, 2016
@tomwilkie
Copy link
Contributor

Write capacity was set to 400/s, which we're almost always trying to do more. Tuning chunk size (#11) should help, but in the mean time I'll make it 1k/s.

@tomwilkie
Copy link
Contributor

That seems to have had a small temporary reduction, but then back to usual - we're still being throttled. I suspect we're just trying to write to much, and the change in provisioned capacity just reset some throttling counter.

@tomwilkie
Copy link
Contributor

Now the ongoing deployment is done, the number of 500s has dropped dramatically (and the dynamodb latency is much improved). So this did have an effect:

screen shot 2016-11-06 at 06 32 00

@tomwilkie
Copy link
Contributor

Fixed by #85

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

No branches or pull requests

2 participants