[chef-dev] Re: Qustions about Chef searching module(couchDB/solr)

[Adam Jacob < >]

1. When we store data, we write it first to the canonical data store (PostgreSQL in chef 11, CouchDB in chef 10) and put the object on a queue to be indexed by solr. 
2. When you search for data, we use the Solr index to retrieve a pointer to the canonical data, and return it to you from the canonical data store. You can retrive partial objects by using the partial search API.
3. I would say you are trying to model something very wrong if you need to hit search every 10 seconds. What are you trying to achieve?

Best,

Adam

From: Xiaoding Bian Cloud Services RANDD - 72410 < "> >
Date: Sunday, August 4, 2013 7:47 AM
To: " "> " < "> >
Subject: [chef-dev] Qustions about Chef searching module(couchDB/solr)

Hi chef-devs:

    I am an engineer from VMware, recently we met a problem when using Chef's searching feature, so I'd like to know if 

anyone can share some knowledge/details about searching module's implementation(we are using Chef-0.10.8). 

   Basically, Chef provides two operations like  "search(:node, "name:node01")" and "node[:name]="node01", node.save".

   I'd like to know when executing node.save or search function, what exact actions chef-server will do, for example:

   (1)When and How does Chef read data from couchdb and update solr indexes?

   (2)when updating solr indexes, does Chef fetch the whole data bag or just the data changed recently.

   (3)If we tend to run search function very frequently, every 10 seconds for example, and the databag maintains hundreds 

       of records, is there potential performance concerns about chef-server/couchdb/solr from your perspective?

Thanks a lot,

-bxd