Re: Long commits lead to rebalance

rtbeats+from+a+background+thread > >Does this resolve your issue? > > >Guozhang > >On Thu, Aug 11, 2016 at 2:47 PM, Sean Morris (semorris) >wrote: > >> I am occasionally seeing commits of offsets taking up to 30 seconds which >> is leading to a rebalance becaus

Long commits lead to rebalance

I am occasionally seeing commits of offsets taking up to 30 seconds which is leading to a rebalance because the consumer hasn't called poll() to heartbeat. I currently have a "heartbeat" routine that runs periodically to handle that I have long processing times of data, and thus don't go back to

Kafka 0.9.0.1 allows offset commits for offsets already committed

I ran in to a strange scenario today that after looking closer I am seeing that Kafka doesn't fail on several invalid scenarios of committing offsets. I have two partitions and two processes in the same consumer group, so each process has one partition. Process 1 retrieved a set of records from

Re: Kafka 0.9.0.1 failing on new leader election

sion of zkclient. > >Can you share the versions of both? And make sure you have only one >zkclient on your classpath? > >On Tue, Jul 26, 2016 at 6:40 AM, Sean Morris (semorris) > wrote: >> I have a setup with 2 brokers and it is going through leader re-election but >> seem

Re: Kafka 0.9.0.1 failing on new leader election

Yes. This is happening after several days of running data, not on initial startup. Thanks. On 7/29/16, 11:54 AM, "David Garcia" wrote: >Well, just a dumb question, but did you include all the brokers in your client >connection properties? > >On 7/29/16, 10:48 AM,

Re: Kafka 0.9.0.1 failing on new leader election

Anyone have any ideas? From: semorris mailto:semor...@cisco.com>> Date: Tuesday, July 26, 2016 at 9:40 AM To: "users@kafka.apache.org" mailto:users@kafka.apache.org>> Subject: Kafka 0.9.0.1 failing on new leader election I have a setup with 2 brokers and it is goin

Kafka 0.9.0.1 failing on new leader election

I have a setup with 2 brokers and it is going through leader re-election but seems to fail to complete. The behavior I start to see is that some published succeed but others will fail with NotLeader exceptions like this java.util.concurrent.ExecutionException: org.apache.kafka.common.errors.No

Re: Consumers disappearing form __consumer_offsets

I have been seeing the same thing and now I understand why. Question is what happens to these topics then after the 24 hours? If I start publishing to them again do the consumers behave properly and only get the new records? Thanks, Sean On 4/11/16, 5:16 PM, "James Cheng" wrote: >This may be re

kafka.admin.ConsumerGroupCommand returns "unknown" for offset and lag

I am using 0.9.0.1 with the new consumer, why am I seeing "unknown" for the offset and lag for some of my topics? /apps/kafka/bin/kafka-run-class.sh kafka.admin.ConsumerGroupCommand --group eoxRulesGroup --bootstrap-server localhost:9092 --new-consumer --describe GROUP, TOPIC, PARTITION, CURRE

Re: Kafka 0.9.0.1 new consumer - when no longer considered beta?

Anyone have any idea? From: semorris mailto:semor...@cisco.com>> Date: Wednesday, March 2, 2016 at 8:36 AM To: "users@kafka.apache.org" mailto:users@kafka.apache.org>> Subject: Kafka 0.9.0.1 new consumer - when no longer considered beta? What are the plans for remo

Kafka 0.9.0.1 new consumer - when no longer considered beta?

What are the plans for removing the "beta" label from the new consumer APIs? Will that be in another 0.9.0.x release? I assume since it has the "beta" label it should not be used in a production environment. Thanks.

Re: Replication Factor and number of brokers

ation. > >HTH, >Damian > >On 16 February 2016 at 14:08, Sean Morris (semorris) >wrote: > >> Should your number of brokers be atleast one more then your replication >> factor of your topic(s)? >> >> So if I have a replication factor of 2, I need atleast 3 brokers? >> >> Thanks, >> Sean >> >>

Replication Factor and number of brokers

Should your number of brokers be atleast one more then your replication factor of your topic(s)? So if I have a replication factor of 2, I need atleast 3 brokers? Thanks, Sean

NotLeaderForPartitionException: This server is not the leader for that topic-partition.

I have suddenly starting having issues where when I am producing data I occasionally get "NotLeaderForPartitionException: This server is not the leader for that topic-partition". I am using Kafka 2.10-0.8.2.1 with the new Producer class and no retries. If I add retries to the Producer propertie