Hello James,
We received this exact same error this past Tuesday (we are on 0.8.2). To
answer at least one of your bullet points -- this is a valid scenario. We
had the same questions, I'm starting to think this is a bug -- thank you
for the reproducing steps!
I looked over the Release Notes to
Hi,
I ran into a scenario where one of my brokers would continually shutdown, with
the error message:
[2016-02-25 00:29:39,236] FATAL [ReplicaFetcherThread-0-1], Halting because log
truncation is not allowed for topic test, Current leader 1's latest offset 0 is
less than replica 2's latest offs
Hi there,
I think what you're asking is how the group protocol can guarantee that
each partition is assigned to one and only consumer in the group at any
point in time. Is that right? The short answer is that it can't. Because of
unexpected pauses on the client (e.g. for garbage collection), there
Hey Guven,
This problem is what KIP-41 was created for:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-41%3A+KafkaConsumer+Max+Records
.
The patch for this was committed yesterday and will be included in 0.10. If
you need something in the shorter term, you could probably use the client
fro
Thanks Ewen. I will get back with findings from my test run using 0.9.0.1
client.
Regards,
Kris
On Tue, Feb 23, 2016 at 9:26 PM, Ewen Cheslack-Postava
wrote:
> Kris,
>
> This is a bit surprising, but handling the bootstrap servers, broker
> failures/retirement, and cluster metadata properly is
hi all,
i'm having trouble processing a topic which includes paths to images which need
to be downloaded and saved to disk (each takes ~3-5 seconds) and several are
received on each poll
within this scenario, i'm receiving the following error:
org.apache.kafka.clients.consumer.CommitFailed
I've opened https://issues.apache.org/jira/browse/KAFKA-3285 to track the
issue.
I will test again with metadata.max.age.ms in mind, that makes sense.
Thanks!
On Wed, Feb 24, 2016 at 8:22 PM, tao xiao wrote:
> One more additional note to new consumer. The new topic will not be picked
> up by n
Hi,
I noticed that in Section 1.3 of the documentation in "Step 3: Create a topic"
the example still use bin/kafka-topics.sh even tho in the deprecation notes of
0.9.0.0 the following is stated:
"Altering topic configuration from the kafka-topics.sh script
(kafka.admin.TopicCommand) has been de
