|author||Brad Hubbard <firstname.lastname@example.org>||2015-09-09 21:04:55 +1000|
|committer||Humble Devassy Chirammal <email@example.com>||2015-09-09 04:18:14 -0700|
Fix trivial typo in done/Features/afr-v1.md
Change-Id: Ia67fe679c3a27bf4e893394d843483431c2b1ac4 Signed-off-by: Brad Hubbard <firstname.lastname@example.org> Reviewed-on: http://review.gluster.org/12139 Reviewed-by: Niels de Vos <email@example.com> Reviewed-by: Humble Devassy Chirammal <firstname.lastname@example.org> Tested-by: Humble Devassy Chirammal <email@example.com>
Diffstat (limited to 'done/Features')
1 files changed, 1 insertions, 1 deletions
diff --git a/done/Features/afr-v1.md b/done/Features/afr-v1.md
index 0ab41a1..83c5f56 100644
@@ -302,7 +302,7 @@ In this step,
- Data self-heal does things a bit differently to make sure no other writes on the file are blocked for the duration of self-heal because files sizes could be as big as 100G(VM files) and we don't want to block all the transactions until the self-heal is over. Locks translator allows two overlapping locks to be granted if they are from same lock owner. Using this what data self-heal does is it takes a small 128k size range lock and unlock previous acquired lock, heals just that 128k chunk and takes next 128k chunk lock and unlock previous lock and moves to the next one. It always makes sure that at least one lock is present on the file by selfheal throughout the duration of self-heal so that two self-heals don't happen in parallel.
- - Data self-heal has two algorithms, where the file can be copied only when there is data mismatch for that chunk called as 'diff' self-heal. The otherone is blind copy of each chunk called 'full' self-heal
+ - Data self-heal has two algorithms, where the file can be copied only when there is data mismatch for that chunk called as 'diff' self-heal. The other one is blind copy of each chunk called 'full' self-heal
3. Change extended attributes to mark new sources after the sync.