Thanks Jiangjie for your help
On Sat, Feb 14, 2015 at 5:59 AM, Joel Koshy wrote:
> Thanks for looking into that!
>
> On Fri, Feb 13, 2015 at 05:31:39AM +, Jiangjie Qin wrote:
> > I think this is the offset checker bug.
> > The offset checker will
> > 1. first check if the offset exists in of
Thanks Joel. But I discover that both MaxLag and FetcherLagMetrics are always
much smaller than the lag shown in offset checker. any reason?
On Sat, Feb 14, 2015 at 7:22 AM, Joel Koshy wrote:
> There are FetcherLagMetrics that you can take a look at. However, it
> is probably easiest to just mon
Jun,
I updated our brokers earlier today with the mentioned patch. A week ago
our brokers used ~380% CPU (out of 400%) quite consistently, and now
they're varying between 250-325% (probably running a bit high right now as
we have some consumers catching up quite some lag), so there's definitely
an
Hi,
Anyone who knows how to solve my problem, please respond..
Regards,
Nitin Kumar Sharma.
On Thu, Feb 12, 2015 at 3:50 PM, nitin sharma
wrote:
> Hi Team,
>
> i need some help in solving my current issue related to
> "kafka-leadership-rebalance"
>
> I have 2 brokers.. i have deployed 2 topi
