From 1a7363bdea77121e708726b81eec4a6bdb4f9dfe Mon Sep 17 00:00:00 2001 From: Ted Kaemming Date: Tue, 8 Dec 2015 22:32:40 -0800 Subject: [PATCH] replica is irrelevant for example --- README.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.txt b/README.txt index 8922941..bfdbea1 100644 --- a/README.txt +++ b/README.txt @@ -31,8 +31,8 @@ Durability Infrequent `fsync` calls can lead to data loss! A server may return a successful response to a produce request without having -flushed the data to disk or forwarded it to any replica. If the primary server -fails before `fsync`ing the AOF, *that data will be lost.* +flushed the data to disk. If the primary server fails before `fsync`ing the +AOF, *that data will be lost.* Compounding this problem, the (now) noncanonical data may have been received by consumers downstream, who marked those offsets as committed. For example, let's