Ryanne, should I use Connect to run MM2?
Now I use connect-mirror-maker.sh driver.
I noticed when I restart M2Ms, all topics that I created before start syncing.
But It doesn't work for newly created topics (after restart).
On 2020/09/21 22:12:13, Ryanne Dolan wrote:
> Oleg, yes you can
Yes, I use connect-mirror-maker.sh.
On 2020/09/21 22:12:13, Ryanne Dolan wrote:
> Oleg, yes you can run multiple MM2s for multiple DCs, and generally that's
> what you want to do. Are you using Connect to run MM2, or the
> connect-mirror-maker.sh driver?
>
> Ryanne
>
> On Mon, Sep 21,
Oleg, yes you can run multiple MM2s for multiple DCs, and generally that's
what you want to do. Are you using Connect to run MM2, or the
connect-mirror-maker.sh driver?
Ryanne
On Mon, Sep 21, 2020, 3:38 PM Oleg Osipov
wrote:
> I use the configuration for M2M for both datacentres
> clusters:
I use the configuration for M2M for both datacentres
clusters:
- {"name": "dc1", "bootstrapServers": ip1}
- {"name": "dc2", "bootstrapServers": ip2}
Do you mean I need use additional names besides 'dc1' and 'dc2'?
On 2020/09/21 17:27:50, nitin agarwal wrote:
> Did you keep the
Did you keep the cluster name the same ? If yes, then it will cause
conflict in metadata stored in MM2 internal topics.
Thanks,
Nitin
On Mon, Sep 21, 2020 at 10:36 PM Oleg Osipov
wrote:
> Hello!
>
> I have two datacenters DC1 and DC2. When I deploy M2M in DC1 or DC2 all
> things look correct.
Hello!
I have two datacenters DC1 and DC2. When I deploy M2M in DC1 or DC2 all things
look correct. I can create a topic, and this topic will be syncronized with
another datacenter. In this case, I have only one mirror maker. But I want to
deploy M2M in each DC. So after I done this, newly
