kafka-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@apache.org
Subject [kafka] branch trunk updated: MINOR: Fix a typo in a comment in config/server.properties (#4373)
Date Thu, 18 Jan 2018 19:32:47 GMT
This is an automated email from the ASF dual-hosted git repository.

jgus pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/kafka.git


The following commit(s) were added to refs/heads/trunk by this push:
     new b2146a1  MINOR: Fix a typo in a comment in config/server.properties (#4373)
b2146a1 is described below

commit b2146a1cba060d6e3baa67d26a5c06ab316e3f92
Author: mulvenna <mulvenna@users.noreply.github.com>
AuthorDate: Thu Jan 18 11:32:44 2018 -0800

    MINOR: Fix a typo in a comment in config/server.properties (#4373)
---
 config/server.properties | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/config/server.properties b/config/server.properties
index dc22404..1775c21 100644
--- a/config/server.properties
+++ b/config/server.properties
@@ -82,7 +82,7 @@ transaction.state.log.min.isr=1
 # There are a few important trade-offs here:
 #    1. Durability: Unflushed data may be lost if you are not using replication.
 #    2. Latency: Very large flush intervals may lead to latency spikes when the flush does
occur as there will be a lot of data to flush.
-#    3. Throughput: The flush is generally the most expensive operation, and a small flush
interval may lead to exceessive seeks.
+#    3. Throughput: The flush is generally the most expensive operation, and a small flush
interval may lead to excessive seeks.
 # The settings below allow one to configure the flush policy to flush data after a period
of time or
 # every N messages (or both). This can be done globally and overridden on a per-topic basis.
 

-- 
To stop receiving notification emails like this one, please contact
['"commits@kafka.apache.org" <commits@kafka.apache.org>'].

Mime
View raw message