Hey,
yes, at first it specified client.id in the config (I was not sure if which
one is needed):
source->destination.producer.client.id = "mm2"
source->destination.consumer.client.id = "mm2"
source.producer.client.id = "mm2"
source.consumer.client.id = "mm2"
destination.producer.client.id = "
Peter, have you tried overriding the client ID used by MM2's consumers?
Otherwise, the client IDs are dynamic, which would make it difficult to
throttle using quotas.
Ryanne
On Wed, Jan 8, 2020, 10:12 AM Péter Sinóros-Szabó
wrote:
> Hi,
>
> I'd like to throttle the mirroring process when I star
Hi,
I'd like to throttle the mirroring process when I start Mirror Maker 2 at
the first time, so it starts to pull all the messages that exists on the
source cluster. I'd like to do this only to avoid putting too much traffic
on the source cluster that may slow down existing production client on i
