Bug #9223
Updated by Peter Amstutz almost 8 years ago
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.