gitlab-com-seaweedfs/seaweedfs
1
0
Fork 0
mirror of https://github.com/seaweedfs/seaweedfs.git synced 2024-01-19 02:48:24 +00:00
Code Issues Projects Releases Wiki Activity

Updated Erasure coding for warm storage (markdown)

Chris Lu 2019-06-06 01:50:44 -07:00
parent fab41b846c
commit 2f81310581
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
Erasure-coding-for-warm-storage.md

@ -38,7 +38,7 @@ For example, one read request for 3,0144448888 will:
2. The read client can randomly pick one of the returned volume servers, A.
3. Server A will read its index file, find the right volume server B that has the file content. Sometimes it may have to contact additional servers if the file is split between multiple blocks. But usually the data shard has 1GB block size. So this does not happen often.
So in normal operations, there are usually one extra network hop compared to normal volume reads.
In normal operations, there are usually one extra network hop compared to normal volume reads.
In case of missing data shards or read failures from server B, server A will try to collect as many pieces of data as possible from the remaining servers, and compute the required data.