Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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 verify two or more object replicas (instances) exist in the cluster before the client write request is completed.

...

  • Globally, set the configuration file to enabling (recommended) or disabling cluster-wide ROW.

  • Programmatically, use a replicate query argument whenever you need needing to override the cluster-wide ROW configuration.

  • Creating or updating a bucket. The replicate=immediate option quickly invalidates cached bucket versions in the cluster so that the latest version will be is implemented in the cluster. It also prevents subsequent permission errors because out-of-date permissions are used from the prior version.

...

Use this argument to limit or disable ROW for the request if you have cluster-wide ROW is enabled (recommended):

  • replicate=x (where x is an integer) creates x replicas on write. For example, replicate=1 allows the write to succeed with only one instance of the object.

Use these arguments to enable ROW for the request if you have cluster-wide ROW is disabled:

  • replicate=immediate is replicate=2, which verifies two replicas are written.

  • replicate=full is replicate={# of reps specified by lifepoint, or else policy.replicas default}

In every case, the number of replicas Swarm makes synchronously on the request cannot exceed the number of replicas specified in the lifepoint (or, if none, policy.replicas default). For example, for an object with no lifepoint specified, in a cluster with default=2, making a request with replicate=3 will still only cause causes 2 replicas to be synchronously created on the request.

...

Although sometimes a ROW request can return successfully with only one replica created, it will never attempt attempts to do perform the operation if it cannot find at least two nodes up front.

...

If the requested number of replicas does not match the Replica-Count header value, repeat the request. Otherwise, the Health Processor will create creates the additional replicas at a later time.

...