- From: Noah Kantrowitz <
>
- To:
- Subject: [chef] Re: Race Conditions
- Date: Fri, 27 Sep 2013 01:49:19 -0500
All Chef APIs are last-writer-wins at a per-object level.
--Noah
On Sep 27, 2013, at 1:44 AM, Greg Zapp
<
>
wrote:
>
Hello,
>
>
I have a few nagging questions about Chef. One of them revolves around
>
potential race conditions in updating nodes and databags on Chef Server.
>
For the life of me I am unable to find any information on how Chef updates
>
node information on the server side. Does it merge changed keys? Does it
>
fully overwrite all json keys? If a client run starts and then some
>
external force updates the node on the server, will node.save(s) on the
>
client overwrite that information? What about data bags?
>
>
I would appreciate any information that could be provided on this topic.
>
I'm considering drastic measures to to my lack of understanding of the
>
internals:
>
*Only nodes update their attributes
>
*Databags have ONE writer, multiple readers
>
*Desired state stored in data bags
>
*Current state stored in node attributes or other data bags
>
>
@.@
>
>
>
Thanks,
>
Greg
Attachment:
signature.asc
Description: Message signed with OpenPGP using GPGMail
Archive powered by MHonArc 2.6.16.