Monitoring the lag in bytes makes sense. The only difficulty is currently,
the high watermark in the leader is represented in logical message offset,
not the byte offset. For now, you will have to do the bytes to messages
translation yourself.

As for setting replica.lag.max.messages, you can observe the max lag in the
follower and set replica.lag.max.messages to be a bit larger than that. I
am curious to know the observed max lag in your use case.


On Tue, Sep 10, 2013 at 6:46 AM, Yu, Libo <[EMAIL PROTECTED]> wrote:
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB