[chef] Re: Re: Re: Latency on search indicies

[Jeppe Nejsum Madsen < >]

Peter Donald 
<
 >
 writes:

> Hi,
>
> On Tue, Jun 25, 2013 at 10:46 AM, Brad Knowles 
> <
 >
>  wrote:
>>> Just be warned that the lag can be much more significant. We run the
>>> open source variant of chef for now and have noticed lags of anywhere
>>> between <1s to ~120s between the data being inserted and it being
>>> accessible via search.
>>
>> What version of chef-server are you running?  Is it Chef 11.x, 10.x, or 
>> something older?
>
> We actually use Chef 11 but to be honest most of the strategies we
> used to address this were developed when we were on 10.x. 

We're using windows as well. Can you outline what strategies you used?


[...]

> Also most of those other sites can probably afford to rely on eventual
> consistency.

Probably depends on the workflow....

When we add nodes to e.g. an environment and kick of chef-client, it's
unfortunate that only some of the nodes get hit.

> However it would be nice to have the parameter to the rest endpoints
> to block until indexing of the changed data is complete.

Indeed. Otherwise we have to implement this explicitly as you mentioned
by waiting to make sure indices are updated.

/Jeppe