Issue #2701 has been updated by Luke Kanies.

Category set to plumbing
Status changed from Unreviewed to Accepted
Target version set to Rowlf

The only real choice here is to replace the yaml file with a database of some 
kind that can do partial loading.  This is pretty complicated, and likely won't 
actually make it into rowlf, but I'd like to try, anyway.
----------------------------------------
Bug #2701: Memory Leak in Puppet state
http://projects.reductivelabs.com/issues/2701

Author: Greg Boug
Status: Accepted
Priority: Normal
Assigned to: 
Category: plumbing
Target version: Rowlf
Affected version: 0.24.8
Keywords: 
Branch: 


I have a puppet daemon running tidy to clean up a very busy directory (cleans 
several thousand files each week). Using a tidy object: 

 tidy { "/tps/reports":
  age => 1d,
  recurse => true,
  rmdirs => true,
  loglevel => info,
  type => mtime,
 }

The tidy works well, but every file gets recorded into state.yaml, even the 
ones that were removed several months ago. When Puppet reads in this yaml file 
it gets progressively bigger which consumes a significant chunk of memory on 
the host (I just killed a Puppet daemon with approx 900Mb resident, 
for example - this had been running approx. 2 weeks)

My workaround for now is that I wipe the state.yaml file and restart puppet 
periodically - usually every couple of weeks or so... Another workaround I have 
is to run the attached script periodically and restart puppet. The script culls 
all references to Tidy objects from the database - preserving the rest of the 
state database.


-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://reductivelabs.com/redmine/my/account

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/puppet-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to