...
The Replicate on Write (ROW) option forces Swarm to write a new object to one or more additional nodes before returning a success status. Using this content protection option, you can ensure that verify two or more object replicas (instances) exist in the cluster before the client write request is completed.
...
Use these arguments to enable ROW for the request tf if you have cluster-wide ROW disabled:
replicate=immediate is replicate=2, which ensures that verifies two replicas are written.
replicate=full is replicate={# of reps specified by lifepoint, or else
policy.replicas default}
...
Swarm indicates the number of replica created with the request in the Replica-Count header. To ensure you received the correct number of replicas, check the Check the header value in the response .If to verify the correct number of replicas is received.
Swarm returns a 412 Preconditioned Failed response if Swarm cannot locate at least two nodes in the cluster that will can replicate the object, it will return a 412 Preconditioned Failed response. However, . Swarm proceeds with the request if Swarm can locate a PAN and one ROW peer node, it proceeds with the request.
Although sometimes a ROW request can return successfully with only one replica created, it will never attempt to do the operation if it cannot find at least two nodes up front.
Responses for replicating objects
If Swarm returns a 412 Preconditioned Failed response if Swarm is replicating an object and the cluster cannot locate at least two nodes to store the replicas initially, it .
Swarm returns a 412 Preconditioned Failed response.If 201 Created response if Swarm locates one node to store the replica, it returns a 201 Created response. Applications that need to verify the requested number of created replicas should check the Replica-Count header value to verify how many replicas were created in the cluster.
...