-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
InfluxDB 0.9 behind ELB results in 503s #3102
Comments
I built influxd from source and had it save pprof data ( top30:
top30 -cum:
|
Looks like we're not caching the authenticated info so it's bcrypting the password on every request, which is killing the CPU. Will prioritize this one. |
Thanks for the additional info and investigation btw! |
Glad to help make an awesome product even better! |
dgnorton
added a commit
that referenced
this issue
Jun 26, 2015
dgnorton
added a commit
that referenced
this issue
Jun 26, 2015
dgnorton
added a commit
that referenced
this issue
Jun 26, 2015
dgnorton
added a commit
that referenced
this issue
Jun 29, 2015
dgnorton
added a commit
that referenced
this issue
Jun 29, 2015
dgnorton
added a commit
that referenced
this issue
Jun 29, 2015
dgnorton
added a commit
that referenced
this issue
Jun 30, 2015
dgnorton
added a commit
that referenced
this issue
Jun 30, 2015
dgnorton
added a commit
that referenced
this issue
Jun 30, 2015
dgnorton
added a commit
that referenced
this issue
Jun 30, 2015
dgnorton
added a commit
that referenced
this issue
Jun 30, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We just upgraded from InfluxDB 0.8 to 0.9 and are now seeing many
503 Service Unavailable: Back-end server is at capacity
from AWS load balancers.Beneath is a graph from CloudWatch. 0.9 was deployed around 08:00:
CPU load on InfluxDB instance is higher:
The health check is working. My guess is that it has to do with instances refusing socket connections.
The 503s happen both for writes and reads. We use Grafana for monitoring. When Grafana makes a batch of requests to update graphs, usually one or two requests are OK and the rest fails with 503s.
Is this a bug or should we simply avoid using ELB? We use it primarily because of Route53's aliasing and for SSL termination.
The text was updated successfully, but these errors were encountered: