Though this behavior is not expected , I’ll suggest not to use chef as a
file server to distribute large binaries or config files . use NFS or a
vanilla lighthttpd server in to host the file and remotely_file resource
inside the chef recipes to install it instead.
For getting the root cause you can use ruby-prof with kcachegrind to check
which part of the close is actually consuming large memory
On Jun 30, 2013 6:21 AM, “Yonah Russ” email@example.com wrote:
I have a simple resource as follows:
cookbook_file “/opt/local/share/da.json” do
notifies :reload, resources(:service => “apache”)
The source file is 8MB.
When chef needs to create this file, it suddenly consumes 750+MB of swap.
Is this a known bug? Any recommendations on a workaround other than not