Re: Broker Exception: Attempt to read with a maximum offset less than start offset

2016-01-28 Thread Manu Zhang
I can reproduce this on 0.9.0.0. The error log is [2016-01-28 16:12:32,840] ERROR [Replica Manager on Broker 1]: Error processing fetch operation on partition [ad-events,1] offset 75510318 (kafka.server.ReplicaManager) I also print the sent offset from producer time partition offset 16:12:32.8

Re: Broker Exception: Attempt to read with a maximum offset less than start offset

2016-01-27 Thread Robert Metzger
Yes, I've asked the user to test with the 0.9.0.0 release (I saw Gwen's comment in KAFKA-725). I have a potentially related question: Is it an issue that both Flink and Gearpump* are not committing their offsets through the SimpleConsumer API? Flink is directly committing the offsets into ZK (and

Re: Broker Exception: Attempt to read with a maximum offset less than start offset

2016-01-27 Thread Ismael Juma
Hi Manu and Robert, It would help to know if this still happens in trunk or the 0.9.0 branch. Ismael On 27 Jan 2016 13:05, "Robert Metzger" wrote: > Hi Manu, > > in the streaming-benchmark, are seeing the issue only when reading with > Gearpump, or is it triggered by a different processing fram

Re: Broker Exception: Attempt to read with a maximum offset less than start offset

2016-01-27 Thread Robert Metzger
Hi Manu, in the streaming-benchmark, are seeing the issue only when reading with Gearpump, or is it triggered by a different processing framework as well? I'm asking because there is a Flink user who is using Kafka 0.8.2.1 as well who's reporting a very similar issue on SO: http://stackoverflow.c

Re: Broker Exception: Attempt to read with a maximum offset less than start offset

2016-01-20 Thread Manu Zhang
Hi, Any suggestions for this issue or do I need to provide more information ? Any links I can refer to would be also very helpful. Thanks, Manu Zhang On Tue, Jan 19, 2016 at 8:41 PM, Manu Zhang wrote: > Hi all, > > Is KAFKA-725 Broker Exception: Attempt to read with a maximum offset less > th

Re: broker exception

2013-11-14 Thread Jun Rao
ge to our configuration > and keep monitoring it. Thanks. > > Regards, > > Libo > > > -Original Message- > From: Jun Rao [mailto:jun...@gmail.com] > Sent: Thursday, November 14, 2013 12:27 PM > To: users@kafka.apache.org > Subject: Re: broker exception > > Are y

RE: broker exception

2013-11-14 Thread Yu, Libo
...@gmail.com] Sent: Thursday, November 14, 2013 12:27 PM To: users@kafka.apache.org Subject: Re: broker exception Are you using ZK 3.3.4? This seems to be caused by a bug in 3.3.3 and 3.3.0. https://issues.apache.org/jira/browse/ZOOKEEPER-1115 Thanks, Jun On Thu, Nov 14, 2013 at 5:25 AM, Yu, Libo

Re: broker exception

2013-11-14 Thread Jun Rao
Are you using ZK 3.3.4? This seems to be caused by a bug in 3.3.3 and 3.3.0. https://issues.apache.org/jira/browse/ZOOKEEPER-1115 Thanks, Jun On Thu, Nov 14, 2013 at 5:25 AM, Yu, Libo wrote: > Hi team, > > This exception occurs regularly on our brokers. When it occurs, a broker > will lose i