t" the returned offset is actually the "logEndOffset", which
> is
> > the offset of the next message that will be appended to the log.
> >
> > Guozhang
> >
> >
> > On Thu, Jul 17, 2014 at 5:26 AM, Tanguy tlrx wrote:
> >
> >>
-- Forwarded message --
From: Tanguy tlrx
Date: 2013-10-10 11:19 GMT+02:00
Subject: Subscribe
To: users@kafka.apache.org
--
-- Tanguy
twitter @tlrx
https://github.com/tlrx
Hi all,
I have a strange behavior with Kafka 0.8.1.1 where consumers do not
retrieve the latest messages.
I created a topic called "my-topic" with 8 partitions. My application
creates a SimpleConsumer instance for each topic-partition pair and
executes an OffsetRequest to retrieve the earliest an
Hi all,
I have a strange behavior with Kafka 0.8.1.1 where consumers do not
retrieve the latest messages.
I created a topic called "my-topic" with 8 partitions. My application
creates a SimpleConsumer instance for each topic-partition pair and
executes an OffsetRequest to retrieve the earliest an
gt; to createMessageStreams()
>
> Thanks,
> Neha
> On Oct 11, 2013 6:10 AM, "Tanguy tlrx" wrote:
>
> > Thanks Jun,
> >
> > Jira issue has been filled:
> > https://issues.apache.org/jira/browse/KAFKA-1083
> >
> > By the way, what is the re
n a random consumer
> id by default. You can try setting "consumer.id" to use a fixed consumer
> id. In any case, we probably should deregister those beans when shutting
> down the connector. Could you file a jira?
>
> Thanks,
>
> Jun
>
>
> On Thu, Oct 10, 2013 at
8? JMX won't allow a bean with the same name to be
> registered twice. Do you see 2 beans with similar names? What are the exact
> bean names?
>
> Thanks,
>
> Jun
>
>
> On Thu, Oct 10, 2013 at 2:42 AM, Tanguy tlrx wrote:
>
> > Hi all,
> >
> >
Hi all,
In our application, we are currently starting a Kafka Consumer with the
following lines of code:
connector = Consumer.createJavaConsumerConnector(consumerConfig);
streams = connector .createMessageStreams(map);
Then, each KafkaStream is processed in a dedicated thread per topic and
parti
