Nothing painful really at this point.
We were just evaluating kafka, and noticed the discrepancy. Was wondering
what's the 'design way' of using that tool.
Unlikely we gonna use it for prod monitoring at all. Just for initial
experiments.
On Tue, Jul 11, 2017 at 1:23 PM, Jan Filipiak
Hi,
very likely due to timing. What problem is it causing you exactly that
you want to work around?
These differences shouldn't concern you to much I guess.
We use the tool across continents and don't worry about it to much.
Offset Commit interval makes everything blury anyways. If you can
Guys, let me up this one again. Still looking for comments about
kafka-consumer-groups.sh
tool.
Thank you.
On Fri, Jul 7, 2017 at 3:14 PM, Dmitriy Vsekhvalnov
wrote:
> I've tried 3 brokers on command line, like that:
>
> /usr/local/kafka/bin/kafka-consumer-groups.sh
I've tried 3 brokers on command line, like that:
/usr/local/kafka/bin/kafka-consumer-groups.sh --bootstrap-server
broker:9092,broker_2:9092,broker_3:9092 --new-consumer --group logging-svc
--describe
it doesn't make any difference, still x10 times difference in figures when
running on broker
kafka-consumer-groups.sh --bootstrap-server broker:9092 --new-consumer
--group service-group --describe
how many brokers do you have in the cluster? if you have more than one,
list them all using a comma csv with --bootstrap-server.
Also, could you paste some results from the console printout?
Hi all,
question about lag checking. We've tried to periodically sample consumer
lag with:
kafka-consumer-groups.sh --bootstrap-server broker:9092 --new-consumer
--group service-group --describe
it's all fine, but depending on host we run it from it gives different
results.
E.g:
- when