After redeploying several times to try and reproduce this, I've a managed to narrow it down to the way we have "proxy-logging" configured in the proxy pipeline
With this ^^ if I try to swift download a certain image, the memory usage of swift-proxy just increases until it gets killed, every time.
Doing what is in several online examples and adding it twice, like this
pipeline = catch_errors healthcheck proxy-logging cache ratelimit bulk tempurl formpost authtoken keystone staticweb proxy-logging proxy-server
Removes the problem and the swift-proxy memory usages stays stable,
The problem appears to be related to the image also, as I can reliably reproduce this with a certain image and not others. Perhaps we started hitting this recently because the image went over a certain size...
I'll see if I can narrow this down a little further and then submit a patch to puppet-swift.
After redeploying several times to try and reproduce this, I've a managed to narrow it down to the way we have "proxy-logging" configured in the proxy pipeline
We have,
pipeline = catch_errors healthcheck cache ratelimit bulk tempurl formpost authtoken keystone staticweb proxy-logging proxy-server
With this ^^ if I try to swift download a certain image, the memory usage of swift-proxy just increases until it gets killed, every time.
Doing what is in several online examples and adding it twice, like this
pipeline = catch_errors healthcheck proxy-logging cache ratelimit bulk tempurl formpost authtoken keystone staticweb proxy-logging proxy-server
Removes the problem and the swift-proxy memory usages stays stable,
The problem appears to be related to the image also, as I can reliably reproduce this with a certain image and not others. Perhaps we started hitting this recently because the image went over a certain size...
I'll see if I can narrow this down a little further and then submit a patch to puppet-swift.