[chef] Re: Re: Re: Re: Re: Chef 11 in production

[Anton K < >]

> Based on my investigation, the same bug is present in both 10.x and 11.x release tracks, but is completely worked around by running the chef-client with --fork. If you're not seeing any problem with 10.24, then you shouldn't have a problem with 11.4 either.

I found that chef-client 11.x in forked state generate many processes with each call. Like this:

root     27101  0.0  1.7 107876 29384 ?        Sl   10:45   0:00 /opt/chef/embedded/bin/ruby /usr/bin/chef-client -d -f -P /var/run/chef/client.pid -c /etc/chef/client.rb -i 180 -s 20 -L /var/log/chef/client.log

root     27858  0.0  1.7 107876 29380 ?        Sl   10:45   0:00 /opt/chef/embedded/bin/ruby /usr/bin/chef-client -d -f -P /var/run/chef/client.pid -c /etc/chef/client.rb -i 180 -s 20 -L /var/log/chef/client.log

Chef-client 10.x does not have this problem with fork.

In the end, I've stopped at 11.2.0. This version free of memory leak(as my investigation) without fork mode.

On Sat, Apr 20, 2013 at 1:20 AM, Daniel DeLeo < " target="_blank"> > wrote:

On Thursday, April 18, 2013 at 11:14 PM, Anton K wrote:

Thank you for the answers. I've started to use chef-server(11) in a production, but still using chef-client 10.24.0 at the workstation and nodes, because of memory leak problems with 11.4.0.

http://tickets.opscode.com/browse/CHEF-3432

Based on my investigation, the same bug is present in both 10.x and 11.x release tracks, but is completely worked around by running the chef-client with --fork. If you're not seeing any problem with 10.24, then you shouldn't have a problem with 11.4 either.

-- 

Daniel DeLeo