| Table of Contents |
|---|
Swarm can provide protection on disk by creating multiple copies of each object on different nodes called replicas. Control how many replicas are created for each object and how quickly they are created after the object is initially stored in the cluster.
...
While this creates the best balance of throughput and fault tolerance in most circumstances, there are cases where you might want to provide the replication task the same priority as reads and writes, which ensures guarantees replication occurs quickly even under heavy sustained loads.
...
Without ROW, the client writes a single copy and depends on the Health Processor (HP) to create the necessary replicas. Relying on HP leaves open a small window for data loss: the volume containing the node holding the sole copy can fail before HP completes replication. ROW eliminates the window by guaranteeing all replicas are written on the initial request.
How it works: The ROW feature requires Swarm to create replicas in parallel before it returns a success response to the client. ROW protection applies to WRITE, UPDATE, COPY, and APPEND requests. The secondary access node (SAN) sets up connections to the number of available peers required to create the needed replicas when ROW is enabled.
...