[chef] Re: Re: Re: Reindexing and chef-client

[Jesse Nelson < >]

Couple things I can think of:

You can block server's API port with iptables. Causing node client
runs to fail, but not change anything.

Add to all nodes runlist in the front a recipe that simply ends the
run with node.exit.  Till you're done with your upgrade of course.

Knife ssh disable all your clients :)

I am sure there are more!

On Wed, Feb 22, 2012 at 7:03 PM, Jason J. W. Williams
<
 >
 wrote:
> On Wed, Feb 22, 2012 at 7:57 PM, Jesse Nelson 
> <
 >
>  wrote:
>> Yes if, for example, you have a search based load balancer it will
>> pull results that will be incomplete while re-indexing is being run.
>> In scenarios I know that a partial or incomplete result would be worse
>> than maintaing current state. I have in the past put checks on results
>> to be in some bounds in an only_if on some resource.
>
> That's exactly our scenario (HAProxy). Is there way to disable
> chef-server while the re-indexing is going on that won't disrupt the
> indexing?
>
> -J