Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Updated code sample and instructions for offset checker

...

The consumer offset checker tool is useful to gauge how well your mirror is keeping up with the source cluster. For  Note that the --zkconnect argument should point to the source cluster's ZooKeeper (DC1 in this scenario). Also, if the topic is not specified, then the tool prints information for all topics under the given consumer group. For example:

Code Block
bin/kafka-run-class.sh kafka.tools.ConsumerOffsetChecker --group KafkaMirror --zkconnect localhostdc1-zookeeper:2181 --topic test-topic
KafkaMirror,topic1,0-0 (Group,Topic,BrokerId-PartitionId)
Group           Topic                          Pid Offset          logSize         Lag             Owner
KafkaMirror = KafkaMirror_jkoshy-ld-1320972386342-beb4bfc9-0
  Consumer offset = 561154288
    test-topic                     0   5               5             = 561,154,288 (0.52G)
0               none
KafkaMirror     test-topic    Log size = 2231392259
              1   3 = 2,231,392,259 (2.08G)
     Consumer lag = 1670237971
    4              = 1,670,237,971 (1.56G)
BROKER INFO
0 -> 127.0.0.1:9092

...

 1               none
KafkaMirror     test-topic                     2   6               9               3               none