Re: Is this a bug or just unintuitive behavior?

There is some discussion going on in https://issues.apache.org/jira/browse/KAFKA-3370 about this, as well. I've added a link to your JIRA about it. -James > On Jan 17, 2017, at 9:35 PM, Jeff Widman wrote: > > Agree on suggesting in the docs

Re: Is this a bug or just unintuitive behavior?

Agree on suggesting in the docs that generally the default offset should be reset to "none" after the mirrormaker is going. There is an edgecase where you want to keep offsets to earliest: When you've got a mirrormaker consumer subscribed to a regex pattern and have auto-topic creation enabled on

Re: Is this a bug or just unintuitive behavior?

I agree that setting the default auto.offset.reset to earliest makes sense (This was actually a default choice Flume made for its Kafka channel to avoid missing the first messages). However I think, at a minimum, we should also document a recommendation to consider changing the value to none after

Re: Is this a bug or just unintuitive behavior?

[Moving discussion from users list to dev list] I agree with Ewen that it's more sensible for mirrormaker to default to replicating topics from the earliest offset available, rather than just replicating from the current offset onward. I filed a JIRA ticket https://issues.apache.org/jira/browse/K