Author: junrao
Date: Wed Aug 21 17:15:35 2013
New Revision: 1516226
URL: http://svn.apache.org/r1516226
Log:
add more jmx in 0.8 doc
Modified:
kafka/site/08/ops.html
Modified: kafka/site/08/ops.html
URL:
http://svn.apache.org/viewvc/kafka/site/08/ops.html?rev=1516226&r1=1516225&r2=1516226&view=diff
==============================================================================
--- kafka/site/08/ops.html (original)
+++ kafka/site/08/ops.html Wed Aug 21 17:15:35 2013
@@ -180,12 +180,14 @@ We pay particular we do graphing and ale
<li>Number of partitions each node is the leader for.
<li>Leader elections: we track each time this happens and how long it
took
<li>Any changes to the ISR
+ <li>The lag in messages per partition in the follower. If a broker is
restarted, these metrics tell you how quickly the followers are catching up.
<li>The number of produce requests waiting on replication to report back
<li>The number of fetch requests waiting on data to arrive
<li>Avg and 99th percentile time for each request for waiting in queue,
local processing, and waiting on other servers
<li>The raw rate of incoming fetch and produce requests
<li>GC time and other stats
<li>Various server stats such as CPU utilization, I/O service time, etc.
+ <li>On the client side, the message/byte rate (global and per topic),
request rate/size/time. On the consumer side, max lag in messages among all
partitions and min fetch request rate. For a consumer to keep up, max lag needs
to be less than a threshold and min fetch rate needs to be larger than 0.
</ul>
<h4>Audit</h4>
