Swift memory usage grows until it is killed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Derek Higgins | ||
Liberty |
Fix Released
|
High
|
Derek Higgins | ||
Mitaka |
Fix Released
|
High
|
Derek Higgins |
Bug Description
On RH2 we've deployed tripleo mitaka on centos7
Everything was going well until we registered the cloud with nodepool, soon after swift got killed by the OOM
Jun 24 01:06:56 overcloud-
it was using 80GB of ram
I restarted swift-proxy and after 30 minutes its back using 63GB
Also nova instances are failing to boot (the image sizes are nearly 6GB so they are chunked in swift), as glance is throwing errors while trying to get the image from swift
File "/usr/lib/
resp_
File "/usr/lib/
headers=
File "/usr/lib/
service_
File "/usr/lib/
conn.
File "/usr/lib/
files=files, **self.
File "/usr/lib/
return self.request_
File "/usr/lib/
resp = self.send(prep, **send_kwargs)
File "/usr/lib/
r = adapter.
File "/usr/lib/
raise ConnectionError
ConnectionError: ('Connection aborted.', BadStatusLine(
tags: | added: alert |
Changed in tripleo: | |
assignee: | nobody → Emilien Macchi (emilienm) |
Changed in tripleo: | |
milestone: | none → newton-3 |
tags: | added: liberty-backport-potential mitaka-backport-potential |
We could switch to use a Glance file backend instead?