Thanks for the explanation.
Ross
On 23 May 2013 07:19, Neha Narkhede wrote:
> Thanks,
> Neha
> On May 21, 2013 5:42 PM, "Ross Black" wrote:
>
> > Hi,
> >
> > I am using Kafka 0.7.1, and using SyncProducer and SimpleConsumer with a
> > single broker service process.
> >
> > I am occasionally
Thanks,
Neha
On May 21, 2013 5:42 PM, "Ross Black" wrote:
> Hi,
>
> I am using Kafka 0.7.1, and using SyncProducer and SimpleConsumer with a
> single broker service process.
>
> I am occasionally seeing messages (from a *single* partition) being
> processed out of order to what I expect and I am
Yes, reconnect.time.interval.ms is a new config that we added to 0.7. Will
update the website.
VIP is a virtual IP on a load balancer. You can associate multiple brokers
with a VIP and the VIP will randomly select one of the brokers to connect
to during socket establish time. The issue is that if
Hi Jun,
Thanks for the quick response.
(I just discovered that you had answered a similar question on the dev list
-
http://mail-archives.apache.org/mod_mbox/kafka-dev/201304.mbox/%3CCAFbh0Q1XSjG2B9iO%2BpDeM8p9RsDDqKA9E8LY5ScXzAncaQ_mVg%40mail.gmail.com%3E
)
I set the following properties on the
In 0.7, each producer reconnects to the broker periodically. Messages sent
in different socket connections could arrive out of order. Take a look at
reconnect.interval in http://kafka.apache.org/07/configuration.html. If you
don't use VIP for the producers, you can actually set reconnect.interval t
Hi,
I am using Kafka 0.7.1, and using SyncProducer and SimpleConsumer with a
single broker service process.
I am occasionally seeing messages (from a *single* partition) being
processed out of order to what I expect and I am trying to find where the
problem lies. The problem may well be in my co
