Multiple and Simultaneous Property Updates
When you use a single function call to set multiple properties for a single object, the cluster applies the changes as follows:
- For networks and network interfaces, the change is applied as a single atomic unit. Either all of the property changes will be applied or none will be applied.
- For groups, nodes, resources, and resource types, the change is not atomic. If a problem occurs during processing, the results are unpredictable. Some or none of the properties may be changed.
When the cluster receives simultaneous property change requests from multiple nodes, it applies the changes as follows:
- For networks and network interfaces, each change is applied individually as an atomic unit. One request will either succeed or fail, then the next will succeed or fail, and so on. The order in which the requests are resolved is first come, first served.
- Simultaneous property changes to groups, nodes, resources, and resource types are applied in an unpredictable order. For changes involving multiple properties, the order of resolution can change from property to property.
For example: Application A on Node A requests that Group N's AutoFailbackType and PersistentState properties be set to value A. At the same time, Application B on Node B requests that the same properties be changed to value B. Each individual property change request can be resolved in any order, resulting in the following possible outcomes.
|Result of A's request||Result of B's request||Final value of AutoFailbackType||Final value of PersistentState|
|Error||Error||no update||no update|
Be sure to verify the results of a property change before relying on the value of the property in subsequent operations.