[chef] Re: Re: Dependency solver overloaded issue

[Daniel DeLeo < >]

On Monday, October 20, 2014 at 9:46 AM, Sean Clemmer wrote:

> Did you ever find a solution to this? We're seeing this exact behavior with 
> our Chef server, and there doesn't seem to be much on this out in the wild


>  
> On Thu, Sep 25, 2014 at 7:06 AM, Michael Hart 
> <
 
>  
> (mailto:
 )>
>  wrote:
> > I’m seeing occasional errors on chef-client runs which cause the runs to 
> > fail. I originally thought it was a resource issue on the chef server 
> > (open source chef server v11.1.1 on Ubuntu LTS) and resized the server, 
> > also set erchef['db_pool_size'] = 40 and postgresql['max_connections'] = 
> > 400. However that doesn’t resolve it.  
> >  
> > I suspect a hint in the erchef error below "msg=no_depsolver_workers”, 
> > but I don’t know how to further debug this one. I’d appreciate any 
> > hints/suggestions. Logs follow:

This isn’t really a bug per se. You’re giving the server more dependency 
solving problems than it can handle at a time. Your options are:
* Increase the number of dep solver workers. This means you’re throwing more 
CPUs at the problem, so it won’t work unless you have spare CPU capacity on 
the server. 
http://docs.getchef.com/config_rb_chef_server_optional_settings.html#erchef
* Use more splay to make chef client run at different times
* Lock down your dependencies to exact versions using environments, to make 
the dependency solving problem easier for the server. This entails some 
workflow changes. The environment cookbook pattern is one way of doing this, 
another is to put all of your cookbooks in one repo and have Ci or some other 
tool generate your environments.


HTH,



--  
Daniel DeLeo