mirror of
https://github.com/schoebel/mars
synced 2024-12-24 23:52:46 +00:00
doc: clarify CRC methods
This commit is contained in:
parent
f111eb339d
commit
8e732922ea
@ -6106,6 +6106,26 @@ Disk failures are regarded as already solved (e.g.
|
||||
already included in the probability of storage node failures.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
We only look at
|
||||
\series bold
|
||||
data replication
|
||||
\series default
|
||||
with a redundancy degree of a relatively small
|
||||
\begin_inset Formula $k$
|
||||
\end_inset
|
||||
|
||||
.
|
||||
CRC methods are not used across storage nodes, but may be present
|
||||
\emph on
|
||||
internally
|
||||
\emph default
|
||||
at some storage nodes, e.g.
|
||||
RAID-5 or RAID-6 or similar methods.
|
||||
Notice that CRC methods generally involve very high overhead, and even
|
||||
won't work in realtime across long distances (geo-redundancy).
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
We restrict ourselves to temporary /
|
||||
\series bold
|
||||
|
Loading…
Reference in New Issue
Block a user