, Oliver Dain
> >> >wrote:
> >> >
> >> >> I just saw https://issues.apache.org/jira/browse/KAFKA-1193 which
> >>seems
> >> >> like it could be the cause of this. Does that sound right? Is there a
> >> >>patch
> >> >&
gt; >wrote:
>> >
>> >> I just saw https://issues.apache.org/jira/browse/KAFKA-1193 which
>>seems
>> >> like it could be the cause of this. Does that sound right? Is there a
>> >>patch
>> >> we can test? Any date/time when this is ex
3 which seems
> >> like it could be the cause of this. Does that sound right? Is there a
> >>patch
> >> we can test? Any date/time when this is expected to be fixed?
> >>
> >> From: New User mailto:od...@3cinteractive.com
> >>
> >> Date: Wednesday, M
ght? Is there a
>>patch
>> we can test? Any date/time when this is expected to be fixed?
>>
>> From: New User mailto:od...@3cinteractive.com>>
>> Date: Wednesday, March 26, 2014 at 11:59 AM
>> To: "users@kafka.apache.org<mailto:users@kafka.apa
day, March 26, 2014 at 11:59 AM
> To: "users@kafka.apache.org<mailto:users@kafka.apache.org>" <
> users@kafka.apache.org<mailto:users@kafka.apache.org>>
> Subject: data loss on replicated topic
>
> My company currently testing Kafka for throughput and fault tole
at 11:59 AM
To: "users@kafka.apache.org<mailto:users@kafka.apache.org>"
mailto:users@kafka.apache.org>>
Subject: data loss on replicated topic
My company currently testing Kafka for throughput and fault tolerance. We’ve
set up a cluster of 5 Kafka brokers and ar
My company currently testing Kafka for throughput and fault tolerance. We've
set up a cluster of 5 Kafka brokers and are publishing to a topic with
replication factor 3 and 100 partitions. We are publishing with
request.required.acks == -1 (e.g. All ISR replicas must ACK before the message
is c
