On Wednesday, March 6, 2013 at 7:35 AM, Chris wrote:
hi chefsi have a question about the solr query that a node does at thebeginning of its run -- this oneselect?q=content:hostname__%3D__*&wt=json&fq=%2BX_CHEF_database_CHEF_X:chef+%2BX_CHEF_type_CHEF_X:node&rows=1000it looks like its asking for a list of every node, which at firstseems fine. but its causing me a lot of grief and i'm wondering whatto do about it.if i query solr in a browser it returns very quickly, and i can evensee that in the solr log when my chef servers run the query. theproblem is that if this list has 400-ish or more entries in it my chefserver nodes start using a ton of cpu and are slow to respond toclients. it seems like the chef servers are having a hard timeprocessing the results. i have 1300 clients split across 2 chefservers (api only. solr, couch, and rabbit are on a different host),each with 8GB and 4 cores. do i simply need more chef server nodes?--Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extentpermitted by applicable law.
Archive powered by MHonArc 2.6.16.