We've been running with the new patch since yesterday, and everything seems
to be working just fine (comparable to the previous patch).
Haven't look into the memory consumption that much though, doesn't look
like it varies too much between the patches.
On Mon Feb 16 2015 at 7:31:34 PM Solon Gordo
We have several dozen topics, each with only one topic (replication factor
or 2).
We are wanting to launch console-consumer for these in a manner that will
support saving offsets (so they can resume where they left off if they need
to be restarted). And I know consumer groups is the mechanism for
Sounds like a potential bug, and it sounds like you can easily reproduce
it. Can you post your test code and a description of the server version and
how you started/configured it, and what you expect to see from your test
and what you actually see:
https://issues.apache.org/jira/browse/KAFKA/
This
don't know whether it is the cause of your issue or not. but "batch.size"
is measured as bytes (not number of messages). default is 16384
On Mon, Feb 16, 2015 at 12:11 PM, ankit tyagi
wrote:
> Hey,
>
> I am doing POC on kafka .8.2.0 version.Currently I am using kafka-client
> of 0.8.2.0 version
Hi,
I am still using 0.8.1.1 because of the CPU use concerns.
I'm confused about why the SimpleConsumer has:
OffsetCommitResponse commitOffsets(OffsetCommitRequest request)
and
OffsetFetchResponse fetchOffsets(OffsetFetchRequest request)
but no way that I can see to issue a ConsumerMetadataRe
Hey,
I am doing POC on kafka .8.2.0 version.Currently I am using kafka-client
of 0.8.2.0 version for producing async message with callBackHandler.
I am using batch.size =1 in my producer cleint. As per my Understanding ,
This should behave like a sync client though message can be published from
d
The following is my kafka cluster setting:
Kafka version: 2.8.0-0.8.0
5 Zookeepers
16 kafka nodes
90 partitions for each of topic
RC: 3
We got a wired issue for Kafka restarting.
1) modify retention hours in server properties (from 72 hours to 168 hours)
2) Rolling restart Kafka nodes one by one
I tested the new patch out and am seeing comparable CPU usage to the
previous patch. As far as I can see, heap usage is also comparable between
the two patches, though I will say that both look significantly better than
0.8.1.1 (~250MB vs. ~1GB).
I'll report back if any new issues come up as I sta
David,
Thanks for sharing this. Any plans to include 0.8.2 to the list of
available packages?
Or, any chance you could share your packaging script? Deb package for
kafka 0.8.2 (or any other version for that matter) is sorely missed.
Thanks,
2015-02-11 21:34 GMT+03:00 David Morales :
> Regarding
Hello,
We've an issue on our Kafka production. (Kafka 0.8.1.1 on 9 Debian Wheezy
servers).
We tried to move a topic from a server to another, but no data was created
on the target.
After some tries when decidec to stop Kafka on this server (kafka3),
removed all topic's data on /var/lib/kafka/*
an
Thank you Todd for your detailed explanation. Currently I export all
metrics to graphite using the reporter configuration. is there a way I can
do similar thing with offset checker?
On Mon, Feb 16, 2015 at 4:21 PM, Todd Palino wrote:
> The reason for this is the mechanic by which each of the lag
The reason for this is the mechanic by which each of the lags are
calculated. MaxLag (and the FetcherLagMetric) are calculated by the
consumer itself using the difference between the offset it knows it is at,
and the offset that the broker has as the end of the partition. The offset
checker, howeve
12 matches
Mail list logo
