Re: Need a help in understanding __consumer_offsets topic creation in Kafka Cluster

Thanks @Stevo Slavić *Thanks, Kunal* *+91-9958189589* *Data Analyst* *First Paper Publication : **http://dl.acm.org/citation.cfm?id=2790798 * *Blog:- **http://learnhardwithkunalgupta.blogspot.in * On Mon

Re: Need a help in understanding __consumer_offsets topic creation in Kafka Cluster

You are affected by this 0.9.0.0 bug https://issues.apache.org/jira/browse/KAFKA-2988 It was fixed for 0.9.0.1. You could just apply same fix to your 0.9.0.0 cluster but I'd recommend upgrading to 0.9.0.1. Kind regards, Stevo Slavic. On Mon, Mar 14, 2016, 07:10 Kunal Gupta wrote: > Hi everyone

Need a help in understanding __consumer_offsets topic creation in Kafka Cluster

Hi everyone, I am new here, recently join the group. I faced a problem in Kafka Cluster, a problem is described below. I am using Kafka version 0.9.0.0 We have established a Kafka Cluster of 3 machines where 2 machines are utilized for Kafka broker and same 3 machines utilized for zookeeper. Whe

Consuming previous messages and from different group.id

Hi everyone, Are there any specific configurations/properties that need to be set at the consumer or at the broker to allow: 1) The same message M1 to be delivered to two consumers that "belong"to different consumer group.idS ? 2) A consumer to receive messages that were sent to broker before

Re: Kafka 0.8.1.1 keeps full GC

other nodes gc log looks like this: [GC 99623.647: [ParNew: 284027K->6782K(314560K), 0.0136660 secs] 818985K->541887K(1013632K), 0.0137850 secs] [Times: user=0.10 sys=0.00, real=0.02 secs] [GC 99636.522: [ParNew: 286398K->9306K(314560K), 0.0149200 secs] 821503K->544533K(1013632K), 0.0150510 secs]

Re: Kafka Streams

Hello Jan, Kafka Streams does implement the repartitioning for certain join / aggregate cases, such that the joining streams and tables will be co-partitioned by the specific keys. This is abstracted from the users that code with the high-level Streams DSL. Since Kafka topic partitions are replic

Re: seekToBeginning doesn't work without auto.offset.reset

Cody, We do not have an umbrella JIRA for this, but rather a case-by-case JIRA ticket / KIP for API changes in consumer. If you feel strong about some specific change on the consumer API, please feel free to create a new KIP with the detailed motivation and proposed modifications. Guozhang On F

Re: Kafka broker decommission steps

Alexis, Yeah I agree with you the admin operations should be reasonably convenient, for example in partition assignment, it should definitely do something more clever than requiring a user-provided json. That is also something that the community has been discussing and working on to improve. Agai

Re: Kafka 0.8.1.1 keeps full GC

Hi, These logs are minor GC logs and they look normal. Look for the word 'Full' for full gc log details. On Sun, Mar 13, 2016 at 3:06 PM, li jinyu wrote: > I'm using Kafka 0.8.1.1, have 10 nodes in a cluster, all are started with > default command: > ./bin/kafka-server-start.sh conf/server

Re: Kafka topic deletion still not working well

Created https://issues.apache.org/jira/browse/KAFKA-3389 and https://issues.apache.org/jira/browse/KAFKA-3390 On Sun, Mar 13, 2016 at 10:11 AM, Stevo Slavić wrote: > Is it normal/expected behavior during topic deletion that to-be-deleted > topic partitions ISR will get updated/shrink as replicas

Kafka 0.8.1.1 keeps full GC

I'm using Kafka 0.8.1.1, have 10 nodes in a cluster, all are started with default command: ./bin/kafka-server-start.sh conf/server.properties but yesterday, I found that two nodes kept full GC(every 1-3 seconds), although there was still enough memory: 99546.435: [GC [1 CMS-initial-mark: 532714K(

Re: Kafka topic deletion still not working well

Is it normal/expected behavior during topic deletion that to-be-deleted topic partitions ISR will get updated/shrink as replicas remove fetcher and delete partition log? On Fri, Mar 11, 2016 at 5:32 PM, Stevo Slavić wrote: > Didn't finish sentence, wanted to change font but managed to hit Send >