yahoo-eng-team team mailing list archive

[Ian Cordasco <ian.cordasco@xxxxxxxxxxxxx>]

So I'm marking this as won't fix. The S3 driver was removed in Mitaka.
Liberty is EOL. Kilo has been EOL for quite a while. Since there's no
driver in master to fix this for, it seems as though it's not worth
fixing.

If you can, however, provide a different configuration that replicates
this behaviour, we can reopen this and consider targeting it to the
appropriate series.

** Changed in: glance
       Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1644711

Title:
  memory leak in glance api when a big image ~300GB is downloaded via
  glanceclient in kilo

Status in Glance:
  Won't Fix

Bug description:
  memory leak in glance api when a big image ~300GB is downloaded via
  glanceclient in kilo.

  the backend store is S3. when the glanceclient starts downloading the
  image, the glanceclient is stopped.

  After stopping the glanceclient process the memory consumed by
  associated glance-api starts increasing every second till it consumes
  70-80% memory  (seen via top) and finally becoming unresponsive.

  Upon restarting the glance-api service the memory consumed is
  released.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1644711/+subscriptions