You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ambari.apache.org by ao...@apache.org on 2015/03/23 15:02:43 UTC
ambari git commit: AMBARI-10172. Remove log.flush.interval.messages
from kafka config templates (aonishuk)
Repository: ambari
Updated Branches:
refs/heads/trunk 8a24c7202 -> 360d4c814
AMBARI-10172. Remove log.flush.interval.messages from kafka config templates (aonishuk)
Project: http://git-wip-us.apache.org/repos/asf/ambari/repo
Commit: http://git-wip-us.apache.org/repos/asf/ambari/commit/360d4c81
Tree: http://git-wip-us.apache.org/repos/asf/ambari/tree/360d4c81
Diff: http://git-wip-us.apache.org/repos/asf/ambari/diff/360d4c81
Branch: refs/heads/trunk
Commit: 360d4c814ef64529a292c8b67c0e12c3d22178d9
Parents: 8a24c72
Author: Andrew Onishuk <ao...@hortonworks.com>
Authored: Mon Mar 23 16:02:16 2015 +0200
Committer: Andrew Onishuk <ao...@hortonworks.com>
Committed: Mon Mar 23 16:02:16 2015 +0200
----------------------------------------------------------------------
.../KAFKA/0.8.1.2.2/configuration/kafka-broker.xml | 7 +------
1 file changed, 1 insertion(+), 6 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/ambari/blob/360d4c81/ambari-server/src/main/resources/common-services/KAFKA/0.8.1.2.2/configuration/kafka-broker.xml
----------------------------------------------------------------------
diff --git a/ambari-server/src/main/resources/common-services/KAFKA/0.8.1.2.2/configuration/kafka-broker.xml b/ambari-server/src/main/resources/common-services/KAFKA/0.8.1.2.2/configuration/kafka-broker.xml
index 1efc2bc..b5efd94 100644
--- a/ambari-server/src/main/resources/common-services/KAFKA/0.8.1.2.2/configuration/kafka-broker.xml
+++ b/ambari-server/src/main/resources/common-services/KAFKA/0.8.1.2.2/configuration/kafka-broker.xml
@@ -155,12 +155,7 @@
The byte interval at which we add an entry to the offset index. When executing a fetch request the server must do a linear scan for up to this many bytes to find the correct position in the log to begin and end the fetch. So setting this value to be larger will mean larger index files (and a bit more memory usage) but less scanning. However the server will never add more than one index entry per log append (even if more than log.index.interval worth of messages are appended). In general you probably don't need to mess with this value.
</description>
</property>
- <property>
- <name>log.flush.interval.messages</name>
- <value>10000</value>
- <description>The number of messages written to a log partition before we force an fsync on the log. Setting this higher will improve performance a lot but will increase the window of data at risk in the event of a crash (though that is usually best addressed through replication). If both this setting and log.flush.interval.ms are both used the log will be flushed when either criteria is met.
- </description>
- </property>
+
<property>
<name>log.flush.scheduler.interval.ms</name>
<value>3000</value>