Re: Question about messages in __consumer_offsets topic

Yup, this got fixed in 0.10.2 https://issues.apache.org/jira/browse/KAFKA-2000 -James > On Feb 23, 2017, at 11:10 AM, Jeff Widman wrote: > > The topic deletion only triggers tombstone on brokers >= 0.10.2, correct? I >

Re: Question about messages in __consumer_offsets topic

The topic deletion only triggers tombstone on brokers >= 0.10.2, correct? I thought there was an outstanding bug report for this in lower versions... On Wed, Feb 22, 2017 at 6:17 PM, Hans Jespersen wrote: > The __consumer_offsets topic should also get a tombstone message as

Re: Question about messages in __consumer_offsets topic

Hi Jun, I ran into the same question today (see thread, subject: Consumer / Streams causes deletes in __consumer_offsets?), and here's what Eno and Guozhang helped me understand: There are broker-level configuration values called "offsets.retention.minutes" and

Re: Question about messages in __consumer_offsets topic

The __consumer_offsets topic should also get a tombstone message as soon as a topic is deleted. -hans /** * Hans Jespersen, Principal Systems Engineer, Confluent Inc. * h...@confluent.io (650)924-2670 */ On Wed, Feb 22, 2017 at 5:59 PM, Jun MA wrote: > Hi Todd, > >

Re: Question about messages in __consumer_offsets topic

Hi Todd, Thank you so much for your reply. I assume that the broker will produce the tombstone to __consumer_offsets topic when the offset expires? I’m curious how broker notices the offset expires? Does it store the offset message in memory and periodically check if someone expires? Thanks,

Question about messages in __consumer_offsets topic

Hi guys, I’m trying to consume from __consumer_offsets topic to get exact committed offset of each consumer. Normally I can see messages like: [eds-els-recopp-jenkins-01-5651,eds-incre-staging-1,0]::[OffsetMetadata[29791925,NO_METADATA],CommitTime 1487090167367,ExpirationTime 1487176567367],