Please help us keep this FAQ up-to-date. If there is an answer that you think can be improved, please help improve it. If you look for an answer that isn't here, and later figure it out, please add it. You don't need permission, it's a wiki.
Table of Contents |
---|
Producers
...
First, try to figure out if the consumer has really stopped or is just slow, using . You can use our tool
Code Block | ||||
---|---|---|---|---|
| ||||
bin/kafka-run-class.sh kafka.tools.ConsumerOffsetChecker \--group consumer-group1 \--zkconnect zkhost:zkport \--topic topic1 consumer-group1,topic1,0-0 (Group,Topic,BrokerId-PartitionId) Owner = consumer-group1-consumer1 Consumer offset = 70121994703 = 70,121,994,703 (65.31G) Log size = 70122018287 = 70,122,018,287 (65.31G) Consumer lag = 23584 = 23,584 (0.00G) |
In 0.8, you can also monitor the MaxLag and the MinFetch jmx bean (see http://kafka.apache.org/documentation.html#monitoring).
If consumer offset is not moving after some time, then consumer is likely to have stopped. If consumer offset is moving, but consumer lag (difference between the end of the log and the consumer offset) is increasing, the consumer is slower than the producer. If the consumer is slow, the typical solution is to increase the degree of parallelism in the consumer. This may require increasing the number of partitions of a topic.
...