There is one fetcher per broker, which is responsible for fetching messages
in all consumed topics whose leader is on that broker. We have seen a
fetcher being killed by a bug in Kafka. Also, if the broker is slow (e.g.
due to I/O contention), the fetch rate could also be slower than expected.
Tha
But I assume this would not be normally you'd want to log (every
incoming producer request?). Maybe just for debugging? Or is it only
for consumer fetch requests?
On Tue, Dec 24, 2013 at 12:50 PM, Guozhang Wang wrote:
> TRACE is lower than INFO so INFO level request logging would also be
> reco
Thanks Jun,
I'm still not 100% clear on this. Is the min-fetch rate per topic, or
is it the lowest fetch rate over all topics? Or is it not topic
specific at all.
What would cause this to slow down? Or is it more a measure of the
consumer's rate at processing messages and ability fetching new
I missed the title of "metric" and thought it was "config". Sorry for the
confusion.
Jun's update has answered it.
On Tue, Dec 24, 2013 at 10:10 AM, Jun Rao wrote:
> I updated http://kafka.apache.org/documentation.html#monitoring
>
> Thanks,
>
> Jun
>
>
> On Mon, Dec 23, 2013 at 10:51 PM, Jaso
This does include the patch of 1112, which means the issue is not fixed.
Drew, could you comment on KAFKA-1112 about how you can reproduce this
issue so we can re-open it?
Guozhang
On Mon, Dec 23, 2013 at 11:03 AM, Drew Goya wrote:
> I'm not sure if I had hard killed the broker but I do have
I updated http://kafka.apache.org/documentation.html#monitoring
Thanks,
Jun
On Mon, Dec 23, 2013 at 10:51 PM, Jason Rosenberg wrote:
> I'm realizing I'm not quite sure what the 'min fetch rate' metrics is
> indicating, for consumers. Can someone offer an explanation?
>
> Is it related to the
Jason,
Do you mean "fetch.min.bytes"?
Guozhang
On Mon, Dec 23, 2013 at 10:51 PM, Jason Rosenberg wrote:
> I'm realizing I'm not quite sure what the 'min fetch rate' metrics is
> indicating, for consumers. Can someone offer an explanation?
>
> Is it related to the 'max lag' metric?
>
> Jason
This OS should be similar to my desktop. Did you try
1. kafka-start-zookeeper
2. kafka-start-server
3. kafka-stop-server
And it does not work for you?
Guozhang
On Mon, Dec 23, 2013 at 2:50 PM, Drew Goya wrote:
> We are running on an Amazon Linux AMI, this is our specific version:
>
> Linux v
TRACE is lower than INFO so INFO level request logging would also be
recorded.
You can check for "Completed XXX request" in the log files to check the
request info with the correlation id.
Guozhang
On Mon, Dec 23, 2013 at 10:46 PM, Jason Rosenberg wrote:
> Hmmm, it looks like I'm enabling all
Hanish,
In this case I believe it is a bug for kill -9 scenario. Could you file a
jira and describe the process to reproduce?
Guozhang
On Mon, Dec 23, 2013 at 7:42 PM, Hanish Bansal <
hanish.bansal.agar...@gmail.com> wrote:
> Sorry last message was sent by mistake.
>
> Hi Guazhang,
>
> Please
Hi, I wanted to reach out if folks are using
https://github.com/cainus/Prozess for a node.js client library? Are there
other node.js implementations folks are using or is that primarily it? Are
there even folks using node.js and producing to kafka broker and want 0.8.0
... 0.8.1 ... etc ... suppo
11 matches
Mail list logo
