- From: Chris <
>
- To:
- Subject: [chef] solr fun
- Date: Wed, 6 Mar 2013 07:35:42 -0800
hi chefs
i have a question about the solr query that a node does at the
beginning of its run -- this one
select?q=content:hostname__%3D__*&wt=json&fq=%2BX_CHEF_database_CHEF_X:chef+%2BX_CHEF_type_CHEF_X:node&rows=1000
it looks like its asking for a list of every node, which at first
seems fine. but its causing me a lot of grief and i'm wondering what
to do about it.
if i query solr in a browser it returns very quickly, and i can even
see that in the solr log when my chef servers run the query. the
problem is that if this list has 400-ish or more entries in it my chef
server nodes start using a ton of cpu and are slow to respond to
clients. it seems like the chef servers are having a hard time
processing the results. i have 1300 clients split across 2 chef
servers (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 extent
permitted by applicable law.
- [chef] solr fun, Chris, 03/06/2013
Archive powered by MHonArc 2.6.16.