Add more description for write_affinity_node_count parameter in the doc.
Change-Id: Iad410a2be4f9a2cd5c53e860b9f91993aa7f2369 Closes-Bug: #1531173
This commit is contained in:
parent
f53cf1043d
commit
e75888b281
@ -463,7 +463,12 @@ Example::
|
|||||||
|
|
||||||
Assuming 3 replicas, this configuration will make object PUTs try
|
Assuming 3 replicas, this configuration will make object PUTs try
|
||||||
storing the object's replicas on up to 6 disks ("2 * replicas") in
|
storing the object's replicas on up to 6 disks ("2 * replicas") in
|
||||||
region 1 ("r1").
|
region 1 ("r1"). Proxy server tries to find 3 devices for storing the
|
||||||
|
object. While a device is unavailable, it queries the ring for the 4th
|
||||||
|
device and so on until 6th device. If the 6th disk is still unavailable,
|
||||||
|
the last replica will be sent to other region. It doesn't mean there'll
|
||||||
|
have 6 replicas in region 1.
|
||||||
|
|
||||||
|
|
||||||
You should be aware that, if you have data coming into SF faster than
|
You should be aware that, if you have data coming into SF faster than
|
||||||
your link to NY can transfer it, then your cluster's data distribution
|
your link to NY can transfer it, then your cluster's data distribution
|
||||||
|
Loading…
Reference in New Issue
Block a user