lsm/seaweedfs
1
0
Fork 0
mirror of https://github.com/seaweedfs/seaweedfs.git synced 2025-11-24 08:46:54 +08:00
Code Issues Actions 17 Packages Projects Releases Wiki Activity

Update replication section of wiki for new format.

Michael Spradling
2024-12-03 22:29:20 -05:00
parent e61a7b6314
commit bdc18edb4e
1 changed files with 12 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

25
Replication.md

@@ -83,17 +83,7 @@ No change to Submitting, Reading, and Deleting files.
*Note: This subject to change.*
Value | Meaning
---|---
000 | no replication, just one copy
001 | replicate once on the same rack
010 | replicate once on a different rack in the same data center
100 | replicate once on a different data center
200 | replicate twice on two other different data center
110 | replicate once on a different rack, and once on a different data center
... | ...
So if the replication type is xyz
The replication type is defined by a 3 digit string as follows:
Column | Meaning
---|---
@@ -101,9 +91,18 @@ Column | Meaning
**y** | number of replica in other racks in the same data center
**z** | number of replica in other servers in the same rack
x,y,z each can be 0, 1, or 2. So there are 9 possible replication types, and can be easily extended.
Each replication type will physically create x+y+z+1 copies of volume data files.
Each digit in the replication string can have a value of 0, 1, or 2, representing the number of additional copies of the data to be maintained in the seaweed cluster beyond the original. Data remains readable as long as at least one replica is accessible. However, writes are permitted only if the number of replicas is achievable based on the configuration values. With these parameters, there are 27 possible replication configurations. Each configuration physically creates x+y+z+1 copies of the data volume.
Here are some possible replication configuration examples and what they mean:
Value | Meaning
---|---
000 | no replication, just one copy
001 | replicate once on the same rack
010 | replicate once on a different rack in the same data center
100 | replicate once on a different data center
200 | replicate twice on two other different data center
110 | replicate once on a different rack within the same data center and once on a different data center
... | ...
## Allocate File Key on specific data center