root
/
kafka
mirror of https://github.com/apache/kafka.git
1
0
Fork 0
Code Issues Actions 2 Packages Projects Releases Wiki Activity

MINOR: Fix table of contents and section numbers in the documentation 

Removed a non-existing reference in table of contents and fixed some section numbers.

Author: Vahid Hashemian <vahidhashemian@us.ibm.com>

Reviewers: Jason Gustafson <jason@confluent.io>

Closes #2004 from vahidhashemian/doc/fix_toc
This commit is contained in:
Vahid Hashemian 2016-10-10 17:09:52 -07:00 committed by Jason Gustafson
parent e972d2afd3
commit 8e9e63138d
2 changed files with 2 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
docs/documentation.html
View File

@ -99,7 +99,6 @@
<li><a href="#datacenters">6.2 Datacenters</a>
<li><a href="#config">6.3 Important Configs</a>
<ul>
<li><a href="#serverconfig">Important Server Configs</a>
<li><a href="#clientconfig">Important Client Configs</a>
<li><a href="#prodconfig">A Production Server Configs</a>
</ul>

4
docs/ops.html
View File

@ -498,7 +498,7 @@ producer.purgatory.purge.interval.requests=100
Our client configuration varies a fair amount between different use cases.
<h3><a id="java" href="#java">Java Version</a></h3>
<h3><a id="java" href="#java">6.4 Java Version</a></h3>
From a security perspective, we recommend you use the latest released version of JDK 1.8 as older freely available versions have disclosed security vulnerabilities.
@ -521,7 +521,7 @@ For reference, here are the stats on one of LinkedIn's busiest clusters (at peak
The tuning looks fairly aggressive, but all of the brokers in that cluster have a 90% GC pause time of about 21ms, and they're doing less than 1 young GC per second.
<h3><a id="hwandos" href="#hwandos">6.4 Hardware and OS</a></h3>
<h3><a id="hwandos" href="#hwandos">6.5 Hardware and OS</a></h3>
We are using dual quad-core Intel Xeon machines with 24GB of memory.
<p>
You need sufficient memory to buffer active readers and writers. You can do a back-of-the-envelope estimate of memory needs by assuming you want to be able to buffer for 30 seconds and compute your memory need as write_throughput*30.