Bug #9223
closed
[Node manager] Uses huge amount of RAM on AWS
Description
When node manager starts on AWS, it quicky uses a huge amount of RAM (2 GiB) despite not doing anything.
I've tracked this down to arvnodeman.computenode.driver.ec2.ComputeNodeDriver._init_image_id which calls libcloud.compute.drivers.ec2.BaseEC2NodeDriver.list_images. It seems that the problem is (a) it is listing a huge number of images (many thousands) and (b) it is retaining a lot of memory even for image records that should be GC'd.
We are currently using libcloud 0.16 on AWS which is an very out of date version.
Updated by Peter Amstutz over 8 years ago
- Description updated (diff)
- Category set to Node Manager
Updated by Peter Amstutz over 8 years ago
As a first try I suggest updating libcloud to the latest version we have packaged (0.20 I think?)
Updated by Tom Morris over 8 years ago
The current version of libcloud is 1.2.1. We should definitely not be using a <1.0 release when 1.0+ is available.
Updated by Peter Amstutz over 8 years ago
The complication is that we're using a fork of libcloud which adds the Azure support that we need. We should try to get that merged upstream but requires allocating some engineering time to move it through the process.
Updated by
Updated by Peter Amstutz over 6 years ago
- Status changed from In Progress to Resolved