Hello Samuel, I tried other consumer config and it worked. Basically, it should follow the pattern `source-cluster-alias.consumer.<consumer_config_name>`. In your case, I think it should be `source-cluster-alias.consumer.auto.offset.reset`. But feel free to try other consumer config and see if they work
On 2020/09/15 20:53:12, Samuel Cantero <scante...@gmail.com> wrote: > I tried this but even the override does not work for me as I can still see > "earliest" on the ConsumerConfig properties. Did you manage actually to > make this work or are you just recommending this config? > > Best, > > On Mon, Sep 14, 2020 at 7:26 PM Ning Zhang <ning2008w...@gmail.com> wrote: > > > Hello Samuel, > > > > I guess you are talking about the case where you start to mirror a new > > topic? If yes, I think the config should be > > `source-cluster-alias.consumer.auto.offset.reset`, instead of `target`, > > because `target` is where the producer of MM2 replicates the messages > > towards, right? > > > > If MM2 mirrors a topic that has been previously mirrored and the consumer > > offsets have preserved, `auto.offset.reset`` should not matter, because MM2 > > always start mirroring from the last known offsets > > > > On 2020/09/10 23:03:16, Samuel Cantero <scante...@gmail.com> wrote: > > > Hello, > > > > > > I'd like to know whether starting mirroring from latest is doable with > > > mirrormaker2. I tried setting the > > > target-cluster-alias.consumer.auto.offset.reset to latest but it doesn't > > > work (for an active/passive setup). Any help would be appreciated. > > > > > > Best, > > > > > >
