mirror of
https://github.com/OpenHFT/Chronicle-Map.git
synced 2021-09-13 01:26:12 +00:00
Initial re-work of documentation
This commit is contained in:
@@ -607,8 +607,7 @@ See link::CM_Tutorial_Behaviour.adoc[CM_Tutorial_Behaviour.adoc] for mre details
|
||||
|
||||
Chronicle Map 3 is able to store entry checksums along with entries. With entry checksums it is
|
||||
possible to identify partially written entries (in case of operating system or power failure while)
|
||||
and corrupted entries (in case of hardware memory or disk corruption) and clean them up during
|
||||
[recovery](#recovery) procedure.
|
||||
and corrupted entries (in case of hardware memory or disk corruption) and clean them up during the <<CM_Tutorial.adoc#Recovery,recovery>> procedure.
|
||||
|
||||
Entry checksums are 32-bit numbers, computed by a hash function with good avalanche effect.
|
||||
Theoretically there is still about a one-billionth chance that after entry corruption it passes the
|
||||
|
||||
Reference in New Issue
Block a user