- From: Philippe Bérard <
>
- To: <
>
- Subject: [chef] RE: Re: Re: CHEF 11 : delay before databag update in search
- Date: Thu, 21 Feb 2013 11:06:07 +0100
Thank you all for these important informations
Regards,
-- Philippe Bérard
-----Message d'origine-----
De : Michael Della Bitta
[mailto:
Envoyé : mercredi 20 février 2013 20:47
À :
Objet : [chef] Re: Re: CHEF 11 : delay before databag update in search
If you guys brought Solr up to version 4, the new soft commit feature lets
you get document visibility latency down to a second.
Michael Della Bitta
------------------------------------------------
Appinions
18 East 41st Street, 2nd Floor
New York, NY 10017-6271
www.appinions.com
Where Influence Isnt a Game
On Wed, Feb 20, 2013 at 2:12 PM, Seth Falcon
<
>
wrote:
>
Hi Philippe,
>
>
On Feb 19, 2013, at 8:18 AM, Philippe Bérard wrote:
>
> It seems that theres a kind of slow update when modifying data in a
databag and searching for this particular value through knife search or
Chef::Search::Query
>
>
Chef uses Solr to index objects for search. The Lucene index makes newly
updated data available for search queries after a commit. This setup is not
new to Chef 11, however, the default tuning of the solr/lucene commit
interval is now set at 60 seconds. On average, you will need to wait 30
seconds before an object update is visible via search. You can tune this in
/etc/chef-server/chef-server.rb like this:
>
>
chef_solr['commit_interval'] = 60000 # in ms
>
>
For very small deployments, you can probably turn this down quite a bit.
>
>
+ seth
>
>
Archive powered by MHonArc 2.6.16.